vSphere Upgrade 5.0 to 6.0 - Part 3
This is the list of services I found on 5.0 from vCenter (top) and SRM (below):
Check you've stopped them all - then we can proceed to SQL. Start by backing up the three SQL Databases to a handy location (I've used C:\Temp):
Next, configure the backup for each as follows, giving each a different name:
Then you should end up with the following files:
Copy them to the new SQL 2014 server:
Restore the Databases one at a time by choosing the "Device" option and browsing to the file:
Do this operation separately for each Database:
Then when they are restored you can edit each to change the compatibility from 100 to 120:
Finally recreate the SQL logins if you are using those or grant permissions to the domain service accoutns if not. Assign DB ownership etc as before. We have to install vCenter before we can recreate the rollup jobs for SQL Agent.
Next go to the new vCenter and configure the DSN's for vCenter and Update Manager and test the connection for each of them:
Now, let's try installing vCenter 6.0U2 and pointing it at an existing database and see where we get!
So - this is new VM, Server 2012R2, DSN pointing at SQL 2014 SP1 but with restored copy of vCenter 5.0 Database, just to be clear!!
Note: the vCenter 6.0 installer checks there are TWO vCPUs for vCenter, make any necessary adjustments to your lab.
Here we go, install External vCenter:
Next confirm the vCenter system name:
Click OK:
SO......this approach will not work. I'll have to perform a vCenter upgrade in place on Server 2008R2 and SQL 2008R2 and THEN perform the replatform and resql tasks afterwards.....darn it! Time to startup all those services again...! I'll cheat and just reboot the 4 legacy VMs..! Don't forget to clean up the databases on SQL 2014.
Don't forget vCenter 6.0 installer checks for TWO vCPU so if you're using a lab increase them now. I've also increased the RAM to 8GB to ensure smooth sailing....
So here we are again....this time performing an in place vCenter upgrade on the old 2008R2 Server VMs:
Once you run the installer it immediately recognises it's performing an upgrade:
Enter the Administrator password and Click OK regarding the linked mode warning shown below:
Click Upgrade to process the VM and transform it to vCenter 6.0. This is a clean and pristine install of vCenter 5.0 so I'm not expecting issues but I've read about a few production systems that ran into difficulty so ensure you have good backups of EVERYTHING if you're doing this live.
So we have a web interface we can log into and let's compare views before we upgrade our second vCenter 5.0:
So no sign of SRM plugin in the web interface of course, I checked the C# client after running the 6.0 client installer, it's still there but doesn't work. One thing I found was trying to login with "lab\administrator" fails but just using "administrator" worked fine. This was in both the Web and C# client. Probably something I need to fix in the SSO. Log in as administrator@vsphere.local to resolve. As you see there is no lab.local domain listed:
We need to define our AD domain here:
And here we add in the Domain Administrator account as a vsphere.local Administrator:
now, log out and test!
We can also upgrade the Update Manager at this point.
Ensure the FQDN is selected. The Download Service is an optional component for DMZ or air gapped situations, you're not missing anything with just the core Update Manager install here.
If we take a look now in the Web and C# client we can see if both Sites are back again. This is using the PSC enhanced linked mode feature:
Note: The configuration change to add in the domain admin user to SSO is only required once as we are using a unified SSO domain (!), so when you check it on Site B you'll see it already is there!
