Installation and migration

You may have noticed the term migration is used and not the word upgrade. This is because migration is exactly what is required; due to vROps 6.0 being such a major architectural change, there is no upgrade in place from the previous versions. This is not seen as a significant drawback, however, as the migration process is very simple and gives you the ability to run both vROps 6.0 and vCOps 5.8.x side by side until you feel like decommissioning the previous vCOps 5.8.x servers.

However, this restriction does have its advantages; the biggest advantage being that it will allow administrators time to get used to the new vROps architecture including the look and feel of the new UI, without the worry of not being able to use the older version if an issue arises.

Tip

Running these two instances of vROps side by side is completely up to your discretion. Keep in mind that if a fresh instance of vROps 6.0 is deployed without migrating data, it will take four weeks for dynamic...