Restore vCenter Server from 6 to 5.5 If Upgrade Fails

Dear Folks,Yesterday I’d a interesting challenge from my follow colleague to restore the vCenter from 6 to 5.5 with using the backup and snapshot.

Initially before migrating doing the task I’ve done the testing in the Lab environment it went fine without any trouble since it is New environment that has been build for this upgrade test.No issue it went awesome.

First on foremost,You have decide the topology how you are going to organize your vCenter in your environment whether it should be reliable and cost effective.I’ve have my demo environment which has SSO,Webservice and vCenter in single machine and DB as external DB with MS SQL 2012 SP1 x64.

I’ve taken the Snapshot of the vCenter with memory quiesce and Full backup of vCenter DB instance has been taken in local DB server drive.

Upgrading the vCenter failed to upgrade due to Anti-virus blocking which clearly mentioned by the fellow blogger on this blog post.Reason behind vCenter upgrade exe trying to access the temp folder and deep security not allowing to access the temp folder execution.

(URL : http://www.sitefixed.com/vcenter-upgrade-failed-internalerror-access-denied/)

So disabled the AV and then proceed with upgrade.Then upgrade got completed without any issue other than prerequisites of the hardware requirement.

Now its time to rollback the vCenter upgrade.All what I did was revert the snapshot and vCenter works fine for 5 minutes.I was happy it works as per the tested the previous tested.But later observe that the vCenter failed to communicate with DB.

Analysis the logs…

2017-04-07T20:20:21.821+05:30 [06612 info ‘Default’] [VdbSchemaLoader::LookupSchemaFromDB] Loaded schema and index information from DB
2017-04-07T20:20:21.827+05:30 [06612 error ‘Default’] Database version id ‘600’ is incompatible with this release of VirtualCenter.

2017-04-07T20:22:21.945+05:30 [06612 error ‘vpxdvpxdMain’] [Vpxd::ServerApp::Init] Init failed: VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)
–> Backtrace:
–> backtrace[00] rip 000000018018b7fa
–> backtrace[01] rip 0000000180104c78
–> backtrace[02] rip 0000000180105f6e
–> backtrace[03] rip 000000018008ff08
–> backtrace[04] rip 0000000001065bac
–> backtrace[05] rip 0000000001086722
–> backtrace[06] rip 00007ff758d6102c
–> backtrace[07] rip 00007ff758d5f8cc
–> backtrace[08] rip 00007ff758f9526b
–> backtrace[09] rip 00007ff9184e5ada
–> backtrace[10] rip 00007ff918d013d2
–> backtrace[11] rip 00007ff9198954e4
–>
2017-04-07T20:22:22.114+05:30 [06612 warning ‘VpxProfiler’] ServerApp::Init [TotalTime] took 120822 ms
2017-04-07T20:22:22.114+05:30 [06612 error ‘Default’] Failed to intialize VMware VirtualCenter. Shutting down…
2017-04-07T20:22:22.120+05:30 [06612 info ‘vpxdvpxdSupportManager’] Wrote uptime information
2017-04-07T20:22:22.121+05:30 [06612 error ‘Default’] Alert:false@ d:/build/ob/bora-2183111/bora/vpx/vpxd/util/vdb.cpp:435
–> Backtrace:
–> backtrace[00] rip 000000018018b7fa
–> backtrace[01] rip 0000000180104c78
–> backtrace[02] rip 0000000180105f6e
–> backtrace[03] rip 000000018009c227
–> backtrace[04] rip 00007ff758462809
–> backtrace[05] rip 00007ff758d5ede2
–> backtrace[06] rip 00007ff758d5f90a
–> backtrace[07] rip 00007ff758f9526b
–> backtrace[08] rip 00007ff9184e5ada
–> backtrace[09] rip 00007ff918d013d2
–> backtrace[10] rip 00007ff9198954e4
–>
2017-04-07T20:22:22.121+05:30 [06612 info ‘utilvpxdVdb’] Registry Item DB 5 value is ’50’
2017-04-07T20:22:22.121+05:30 [06612 info ‘utilvpxdVdb’] [VpxdVdb::SetDBType] Logging in to DSN: HOLAHOLA with username
2017-04-07T20:22:22.282+05:30 [06612 info ‘Default’] [VdbSchemaLoader::LookupSchemaFromDB] Loaded schema and index information from DB
2017-04-07T20:22:22.282+05:30 [06612 error ‘Default’] Database version id ‘600’ is incompatible with this release of VirtualCenter.

2017-04-07T20:24:22.330+05:30 [06612 warning ‘vpxdvpxdMain’] Database not initialized. Nothing to unlock
2017-04-07T20:24:22.337+05:30 [06612 info ‘Default’] Forcing shutdown of VMware VirtualCenter now

So from logs clearly says incompatible DB version ID.I’ve restore the database with backup with overwrite the DB.

 

Note:

  • Logs and Performance information will not be available during the restore.
  • MOID After upgrade and rollback haven’t get changed.

Reference KB :

  1. https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015887
  2. https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2091961

 

Happy Sharing!!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s