I recently have been on a mission to eradicate all vCenter Servers running on Windows and replacing them with the vCenter Server Appliance (VCSA). I’ve been very successful with this with the customers I have worked with, with very little push back. The only down fall with the 6.0 release was that Update Manager (VUM) still had to be on a Windows Sever. I got around this in most cases by creating a vCenter “Helper” Server. I would install VUM, PowerCLI and RVTools – All the essentials!
So, after doing a TON of these migrations by using the GUI, I thought I would give the CLI a shot.
Since vCenter 6.5 was introduced today (11/15/2016), I thought I would try to go through the upgrade process via the CLI. I will be going from VCSA 6.0U2 to VCSA 6.5. This upgrade will migrate your database, as well as migrate you from a Linux appliance onto VMware Photon OS.
Why do it from the CLI? Because, its the cool thing to do!
Note: Make sure all of your plugins are compatible with vCenter 6.5!
Note: Make sure SSH is enabled on your source vCenter prior to upgrade/migration.
First you will need to pick the template that you want to start from. VMware does a great job of telling you what you need to do to get this to work from these templates. To find it, mount the ISO and go to “X:\vcsa-cli-installer\templates\upgrade\vcsa6.0” – Pick the template that works for your scenario and save it locally so that you can make changes that are necessary. I will be using the “embedded_vCSA_on_ESXi.json” template.
I’m not going to spell out what each option is, because VMware has done a great job of spelling that out in the Documentation Center for vSphere/vCenter 6.5.
Second, lets go through the upgrade. If you have VUM deployed on a windows server, you will want to run the upgrade script from the VUM server.
On the VUM server, run the Migration Assistant – Can be found at “X:\migration-assistant\VMware-Migration-Assistant.exe”. When the Migration Assistant starts, it will ask you for the Service Account password for the account you used to connect VUM to vCenter. *Note: Don’t close this window until the migration is completeNow we are going to execute the upgrade via the CLI –
- This will kick off 8 Steps: