Hi,
Five months ago I was halfway through migrating from my vCSA 5.5 to 6.0. I'd completed the move to the 6.0 appliance, upgraded one of my three hosts and moved some (less important) VMs onto the upgraded host to see how they went and called it a night.
That night we got hit by a cryptovirus and had to restore some files from backup (VEEAM).
Of course, I'd neglected to update VEEAM to point to the new vCSA and the backups hadn't run. Luckily the data from the previous backup run was only 28hrs old so I switched off the 6.0 vCSA, powered up the old one and added back the 5.5 hosts. The v6 host was left on its own because the vCSA on 5.5 couldn't manage it.
After some mayhem, VMWare earnt my eternal respect by sorting the whole lot out pretty much automatically and within a couple of hours all the VMs were running on the two remaining hosts.
Now I've just managed to pull myself together and repeat the upgrade!
I'm running with the original two hosts under a new vCSA on 6.0u2. The third host is still disconnected and showing powered-off copies of some of the VMs which have been running happily on my other two hosts for five months.
Now I can re-add the third host, do I have to worry about those out of date copies of the VMs? There seems to be a lot of options, ranging from just re-connecting it and letting VMware sort it out again (seems risky) to nuking the third host from orbit and installing it from scratch again.
Can anyone recommend a course of action?
In the meantime, I'm off to update my VEEAM config