This is part 4 of the vSphere 6.5 Basics, detailing the migration of vCenter Server 6.0 on Windows to vCSA 6.5, including the cleanup and rollback processes.

This is a 6 part series, describing the installation basics of vSphere 6.5:

This post has been constructed using the vCenter Server 6.5.0a (Build 4944578) release.

WARNING – Currently, migrating from vCenter Server 6.0 U3 on Windows (must be U2 variant or earlier) to vCSA 6.5 is not supported. If you try this the upgrade will fail with the error message “A problem has occurred. The source vCenter Server might have been Powered Off during this process. Click on Messages for more information.” and the detailed error message “Internal error occurs during Export of vSphere ESX Agent Manager”. Check the VMware Product Interoperability Matrices – Upgrade Path for the latest information.

During the migration, a new vCSA 6.5 instance is deployed with a temporary IP address, data is copied from vCenter Server 6.0 on Windows (Migration Assistant must be installed) to vCSA 6.5 and then imported into the vCSA 6.5 instance. At the end of the migration you will be left with the vCenter Server 6.0 on Windows VM powered off and the vCSA 6.5 instance running as the migrated vCSA instance with the original IP address and hostname. Do not power on both at the same time, otherwise you will have a duplicate vCenter Server conflict. The vCenter Server 6.0 on Windows instance should only be powered on if you need to rollback.

You will no longer need the separate VUM servers, this functionality is built into vCSA 6.5. This post assumes VUM is not used.

Prerequisites

You have a functioning source vCenter Server 6.0 on Windows instance that you want to migrate.

You have the vCSA 6.5.0a ISO image.

You have a Windows 10/Windows Server 2016 instance that can be used to remotely install the vCenter Server Appliance. You cannot use the Windows Server that vCenter Server 6.0 is running on, because it will be powered off during the migration process.

You have an ESXi host that has enough resources to host the new vCenter Server Appliance.

You have an Ephemeral Portgroup (with vDS – vSS does not support this) configured on the destination ESXi host for the vCenter Server Appliance to connect to.

Functioning NTP and DNS servers with existing populated FQDN for the source vCSA.

Temporary IP Address for the target vCSA instance to use during the migration.

If the same vCenter Server or ESXi host is to be used, a new VM name to use (eg. If you are using vc.<domain> then consider using vc65.<domain>). This can be reclaimed during the cleanup process.

You have temporary access to an account that has the ability to add machines to AD.

Install the vCenter Server Migration Assistant



Access the Console of the vCenter Server 6.0 on Windows instance and browse to the mounted vCSA 6.5.0a ISO image. Browse to the “migration-assistant” path. Double click on the “VMware-Migration-Assistant.exe” file. Enter the SSO Administrator credentials and press the Enter key. Verify that the “Waiting for migration to start…” message appears and then minimize the console. You can now proceed to Stage 1.

Deploy vCSA 6.5 to a remote ESXi host (Stage 1)



Access the Console of the Windows instance and browse to the mounted ISO image. Browse to the “vcsa-ui-installer/win32” path. Double click on the “installer.exe” file. On the vCenter Server Appliance Installer page, press the “Migrate” button. In the “Introduction” window, press “Next”. In the “End user license agreement” window, accept the EULA and press “Next”. In the “Connect to source server” window, enter the FQDN or IP Address of the source vCSA 6.0 instance, the Migration assistant port, the SSO credentials and then press “Next”. In the “Appliance deployment target” window, enter the FQDN or IP Address of the ESXi host or vCenter Server where the target vCSA 6.5 instance will be deployed, the HTTPS port, the root credentials and press “Next”. Press “Yes” to the Certificate Warnings. In the “Set up target appliance VM” window, enter the VM name of the vCenter Server Appliance, set the OS root credentials and press “Next”. In the “Select deployment size” window, select “Tiny, Small, Medium, Large or X-Large”, the Storage size (Default, Large or X-Large) and press “Next”. In the “Select datastore” window, select the target datastore, Enable Thin Disk Mode and press “Next”. In the “Configure network settings” window, select the Network (Portgroup must be ephemeral or vSS), IPv4/IPv6, IP assignment, temporary IP address, Subnet mask, default gateway, DNS servers and press “Next”. In the “Ready to complete stage 1” window, review the settings and press “Finish”. The process of deploying the vCenter Server Appliance to the remote ESXi host or vCenter Server will begin. Be patient, this takes 30 minutes or more. You can use the Embedded Host Client to monitor the install progress and assist in resolving any issues you may have. When the message “Deployment complete” appears, record the vCSA hyperlink and then press “Close” or “Continue” (if the Windows instance can connect to the vCSA instance). You can now proceed to Stage 2.

Migrate to vCSA 6.5 (Stage 2)



Open a browser that can connect to the vCSA instance and enter the vCSA URL (https://<Temp IP Address>:5480/) recorded in Stage 1. If you clicked “Continue” at the end of Stage 1, the installer will connect automatically and jump to step 5. Accept any SSL Certificate exceptions. On the Getting Started page, press the “Set up vCenter Server Appliance” icon. Enter the root password configured during the installation process. In the “Introduction” window, press “Next”. The “Connect to source vCenter Server” window will automatically execute and then proceed to the next step. In the “Join AD Domain” window, enter the AD credentials to join the vCSA instance to the AD domain and press “Next”. In the “Select migration data” window, select the data to be upgraded (Configuration, Configuration/Events/Tasks or Configuration/Events/Tasks/Performance Metrics) and press “Next”. In the “Configure CEIP” window, set the Customer Experience Improvement Program policy and press “Next”. In the “Ready to complete” window, review the settings, acknowledge the “source vCenter Server” backup statement and press “Finish”. Press “OK” to the source vCenter Server Shutdown Warning. The three stage process of upgrading/migrating to the vCenter Server Appliance 6.5 will begin. Be patient, this takes 45 minutes or more. When the message “Complete” appears with the three green ticks for each stage, record the vSphere Web Client and Appliance Getting Started Page hyperlinks and then press “Close”. Open another tab of the browser and enter the URL of the vSphere Web Client (https://<IP Address>:443/vsphere-client/). Enter the original SSO Administrator credentials and press “Login”. The vSphere Web Client will open to the “Home” screen. Verify that all of the services that depend upon vCenter Server are functioning correctly. If all is well, execute the Cleanup process tasks below, otherwise consider the Rollback process below. NOTE: From the Appliance Getting Started Page, you can access the HTML5 vSphere Client, which is partially functional.

Rollback to vCenter Server 6.0 on Windows



Verify the upgrade was a failure and you want to rollback to the vCenter Server 6.0 on Windows VM. Power-off the vCSA 6.5 instance. Power-on the vCenter Server 6.0 on Windows VM. Verify the rollback was completely successful and all services that rely on vCenter Server 6.0 on Windows are correctly functioning. Delete the vCSA 6.5 instance.

Cleanup the vCenter Server 6.0 on Windows VM



Verify the upgrade was completely successful and all services that rely on vCSA 6.5 are correctly functioning. Delete the vCenter Server 6.0 on Windows VM. If applicable, delete the VUM server VM(s). Change the name of the vCSA 6.5 instance to match the system hostname (eg. from vc65.<domain> to vc.<domain>). Perform a storage vMotion to another Datastore. This will change the name of the VM Folder and VM files back to the system name. If you want to use the original Datastore, storage vMotion the vCSA appliance back to the original Datastore. If you do not have a second Datastore, you can power off the vCSA instance and rename the Folder and VM files manually, but you will also have to edit the VMX file accordingly (advanced task).