Good day All,
Welcome back!!!!
Recently we had a very hot request to upgrade VC from 5.5 U3 to 6.5 to support HP Gen 10 Blades in the farm as they dont support 5.5 U3.
As our VC was on a blade Windows 2008 R2 with SQL 2008 R2 we had to do some planning to get this accomplished.. so below are the steps we did..
Pre steps :
1. SQL Database backup
2. Full Server backup
3. Created a Windows 2012 R2 Server with same name kept it as workgroup Server in case P2V fails.
Note: We tried to do P2V but for some reason the P2V would fail at 95% and final sync didn't get completed, so we had a Backup plan and we went with it...
Steps performed during the cutover:
1, Unjoined the physical Server and it was power down.
2. New Virtual Machine with same name was added back to domain.
3. SQL 2008 R2 SP1 was installed
4.VC 5.5 U3 was installed
5. Validated VC was online and able to access
6.Took a snapshot and restored the SQL database backup we took from Physical Server.
7.Server was rebooted and then all the Service came back clean,
8.Connected to Server and all the existing Permissions, Standard Switches,Distributed Switches, VLANs was all in tact.
9.After confirming everything as expected snapshot was deleted
10. As SQL 2008 was old the requirement got little changed and the request was to upgrade SQL to 2014, so we upgrade the SQL 2008R2 SP1, applied Sp2 and then upgraded to SQL 2014 as inplace upgrade.
11. Validated everything was intact and at this point took a snapshot before we proceeding to VC 6.5
12. VC was upgraded from 5.5 to 6.5 and everything was tested out.
13. Last step was to upgrade the Vc license file from 5.5 to 6.5 and apply it on the Server.
So must be wondering no issues at all ??? well any upgrades there will be suprises and below are few we had
1. Auto deploy 5.1 was registered and we had to unregister it..so follow the VMware KB 2041183
2.We had HPDP GRE plugin and we had error saying it will not be upgraded and new to reinstall
3.Last big surprise was we lost all the permissions and roles other things like Standard switches,Distributed switches, VLANS was intact.
So solution was to restore dbo.vpx_access as per the KB 2086548
this pretty much covers the steps, hopefully this helps someone and until next one you all have good day!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Welcome back!!!!
Recently we had a very hot request to upgrade VC from 5.5 U3 to 6.5 to support HP Gen 10 Blades in the farm as they dont support 5.5 U3.
As our VC was on a blade Windows 2008 R2 with SQL 2008 R2 we had to do some planning to get this accomplished.. so below are the steps we did..
Pre steps :
1. SQL Database backup
2. Full Server backup
3. Created a Windows 2012 R2 Server with same name kept it as workgroup Server in case P2V fails.
Note: We tried to do P2V but for some reason the P2V would fail at 95% and final sync didn't get completed, so we had a Backup plan and we went with it...
Steps performed during the cutover:
1, Unjoined the physical Server and it was power down.
2. New Virtual Machine with same name was added back to domain.
3. SQL 2008 R2 SP1 was installed
4.VC 5.5 U3 was installed
5. Validated VC was online and able to access
6.Took a snapshot and restored the SQL database backup we took from Physical Server.
7.Server was rebooted and then all the Service came back clean,
8.Connected to Server and all the existing Permissions, Standard Switches,Distributed Switches, VLANs was all in tact.
9.After confirming everything as expected snapshot was deleted
10. As SQL 2008 was old the requirement got little changed and the request was to upgrade SQL to 2014, so we upgrade the SQL 2008R2 SP1, applied Sp2 and then upgraded to SQL 2014 as inplace upgrade.
11. Validated everything was intact and at this point took a snapshot before we proceeding to VC 6.5
12. VC was upgraded from 5.5 to 6.5 and everything was tested out.
13. Last step was to upgrade the Vc license file from 5.5 to 6.5 and apply it on the Server.
So must be wondering no issues at all ??? well any upgrades there will be suprises and below are few we had
1. Auto deploy 5.1 was registered and we had to unregister it..so follow the VMware KB 2041183
2.We had HPDP GRE plugin and we had error saying it will not be upgraded and new to reinstall
3.Last big surprise was we lost all the permissions and roles other things like Standard switches,Distributed switches, VLANS was intact.
So solution was to restore dbo.vpx_access as per the KB 2086548
this pretty much covers the steps, hopefully this helps someone and until next one you all have good day!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
