VMware have done a stellar job with vROps 6.0 having greatly increased:
- ease of installation – deploy from OVA, enter creds and other details, follow a nice GUI style process and just sit back
- ease of migration from vCOps 5.8.1 and above to vROps 6.0.0 – punch in UI VM’s IP address or DNS name and associated credentials and let the magic happen
- ease of administration – single VM, easy-to-create-use-and-let-others-use custom dashboards, custom reports and several other improvements
Now for the key considerations that this post is really about.
1 – Ensure there are enough resources in your new vROps VM. This includes disk, CPU and RAM. The migration wizard throws some boxes in red (red’s not good, right?) but still lets you proceed. See screen below:
If you proceed without increasing the data disk, there may be problems with importing data or adding adapters or general usage post-installation and migration. No brainer, really.
Shutdown the vROps VM and bump up the data disk, the CPU’s and RAM and then proceed. Note – just add a new disk and the VM will automatically allocate it to the data disk (keep this new disk on the same datastore if possible). You will then be presented with a less forbidding screen:
2 – Ensure your adapters are available and installed in vROps. This includes any storage adapters and platform specific adapters. In my case, I needed the following:
If you proceed without these adapters, data pertinent to these adapters will not be migrated and it wont allow you to migrate later. This warning shows up nicely before you pull the trigger:
3 – Plan for your migration to take a day or so. I needed to import about 260GB and the estimated time was 1 day and several hours:
4. After successful migration and general acceptance, decommission your vCOps environment. Here’s a link for a how-to.