VMware

Any disaster stories migrating from Windows vCenter to the vCenter Appliance? (6.0 to 6.7)

I’ve researched the hell out of this in the past couple of months, and I’m most concerned about reaching a point where the vCenter is completely inoperable after a migration attempt. Some have had disasters which took days and weeks to fix, while the majority seem to be smooth sailing.

Has anyone experienced a situation where their entire vCenter had to be rebuilt due to a failed migration? What kind of gotcha’s do we have to look out for before beginning the process?



View Reddit by XesyliadView Source

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

6 Comments

  1. Yes, I wanted to go from 6.0 windows to 6.7 appliance

    boss said NO

    I insisted

    boss said NO

    I insisted

    boss said NO said goto 6.7 windows then move to appliance

    so I upgraded to 6.7 windows, guess what you cant do….

    so now I wait next version

  2. Just how complex is your cluster and your vCenter config? It’s always important to keep in mind that vCenter is nothing more than an orchestrator; you can completely shut it off and your cluster will continue functioning just fine, including things like HA and FT, so unless you really have a lot invested in customizing your vCenter installation you shouldn’t worry about it too much.

    The most annoying thing in my experience is dealing with recreating the distributed switches, but if you’ve documented the setup or it’s not too complicated, this is more annoying than anything else.

    > Has anyone experienced a situation where their entire vCenter had to be rebuilt due to a failed migration?

    So often that I stopped trying to migrate. These days when a new version rolls out, I just shut down the old one and install the new one.

  3. Biggest pain points for me were/are :

    firewalls blocking the upgrade

    Had one issue with GPO not allowing the registry keys to export. That was a fun one, as client insisted on copying all the historical data to new instance. Each attempt took 4 hours. Spent 3 days fixing that.

    Historical data (events etc) – I would keep minimum info, bit keep the old VM around for any logs.

    VUM also is buggy during the upgrade, sometimes I’ve had to remove it via MOB and reinstall after.

    To be honest, I’ve probably done 30 upgrades over the past 2 years, and I’ve had a 50% first time success rate.

    I’d love to just do a reinstall, but your mileage may vary…

  4. Not exact but close: I had a lot of grief with a 6.5 -> 6.7 vCenter upgrade (VCSA -> VCSA).

    The nice part was that: worse comes to worse, you bring your old vCenter back online. We had a lot of issues (some like 15+ failed upgrades) and the only thing we burned was time and a little bit of vCenter downtime every time we tried to complete the migration.

    It was really frustrating, I think we ended up exporting our configs and deploying them in a new vCenter setup because of the amount of time we were burning trying to get the migration to go, but ultimately there was 0 risk to normal daily operations for us.

  5. No horror stories here. Did it twice, no issues both times. Fairly simple setups. Each one was about 2 sites 7 hosts embedded psc. Both done during production hours. Two tips, one. snapshot current vcenter 6.0 vm . Two, run the migration assistant on on server, not ur laptop. Remember dont attempt to change host name or ip during migration, most successful leaving all settings as is

Leave a Reply