STOP! It's dangerous to upgrade to VMware 6.5 alone. Read this
Please don't be like the admin who failed to update PSC first
If you are not running 5.5, you need to do the 5.0 to 5.5 upgrade. At that point you can then perform this upgrade. The details on how to do this can be found here (PDF, page 44).
It is prudent to check beforehand that all your infrastructure has fully functioning and accurate DNS and time servers. NTP and DNS are key. Another important bit of housekeeping – sometimes admins get caught out when one or more of the virtual machines as a CD-ROM attached to them. Leaving a CD attached prevents live migration between cluster nodes and therefore the host evacuation never gets completed, worse DRS won't work with that VM. Nothing worse than a lopsided cluster! There are plenty of ways to get a list of attached CDs including PowerShell and RVTools (if you haven’t checked this out yet, you are missing an extremely useful tool). For the rest of us, ensure all the PSCs are running the same code revision.
This is easy to do. Just log into the PSC URL, it should show the version in question. Assuming they are all patched to the same release, the next step is the upgrade the PSC. Using the vCenter 6.5 release ISO that you want to go to, run the upgrade for the PSC. PSCs can be snapshotted. You never know when you will need to roll back. You’d be crazy not to. The PSC upgrades should all be done one after the next. The best advice is to do them all one after the other until they are all done.
Once the PSC is at the new patch level, it is now OK to upgrade the vCenter(s). Re-run the installer that was used for the PSC upgrade and use it to run the vCenter upgrade (both components are on the one disk).
It’s important to get the upgrades done as soon as possible because running different code versions is never a good idea. Once installed, check the estate over and make sure it is clean. Look for any nasty warnings or alarms.
Proceed with caution (RTFM)
The last task is to upgrade the hosts. This isn’t so critical and can be staged across a more relaxed timeline. If you haven’t already, learn how to use VUM to automate those host upgrades. It is what VUM was designed for.
One thing that sometimes catches out administrators is that sinking feeling when a legacy setup has a raw device attached. Plan around this and downtime for it!
Other gotchas include checking the VMware Hardware Compatibility List. If you have older hardware, be prepared to bin it! Running hardware that is too old means your virtualization experience is going to be sub-optimal anyhow.
That said, there is a danger that some applications (such as middleware by a certain American company whose first initial is I) that are licensed in terms of CPU capacity ratings rather than per socket. In one specific case of moving from older hardware, I saw the licence cost quadruple. It took years to sort that one out.
As always, it comes down to who is paying for the difference. Take it from someone who has been there – the administrator needs to get the users (or whomever pays for it) onboard and do it early.
Ensure that the VMware hardware versions and tools are upgraded. As always, tools versions first then a virtual hardware upgrade. Again, these don’t have to be done right away but upgrading to new hardware versions brings benefits and VMware tools should always be on the latest version anyhow. A tip... Don’t blindly apply the tools updates. I have seen instances where VMtools caused some odd behaviour (a DLLs was overwritten and screwed some functionality). Snapshot is your friend but remember you can’t use snapshots for hardware upgrades!
Lastly, don’t forget to upgrade those licences and apply them to the hosts and vCenter. Sure, you get a small grace period but things like this can be forgotten. Cue panicked upgrades in the portal and applying them.
The upgrade is very worthwhile but creating a plan and getting the owners/users onboard is the order of the day. The actual process isn’t that bad as long as you follow the documentation.
6.5 brings a lot of new stuff to the table, such as encrypted VMs, increased VM sizes and more intelligent DRS, and that’s just for starters. It’s in your interests to upgrade. ®
Sponsored: Becoming a Pragmatic Security Leader