VCSA

Migration Assistant and Migration Tool

vCenter Server migrations have typically taken massive planning, a lot of effort, and time. The new Migration Tool included in the vCenter Server Appliance (VCSA) 6.5 is a game changer. No longer requiring scripts and many long nights of moving hosts one cluster at a time. The Migration Tool does all the heavy lifting. Copying the configuration and inventory of source vCenter Server by default. The migration workflow includes upgrading from either a Windows vCenter Server 5.5 or 6.0 to VCSA 6.5.

Migration Assistant

The first step of the migration workflow requires running the Migration Assistant (MA). The Migration Assistant serves two purposes. The first is running pre-checks on the source Windows vCenter Server. The Migration Assistant displays warnings of installed extensions and provides a resolution for each. It will also show the source and the destination deployment types. Keep in mind changing a deployment type is not allowed during the migration workflow. More information on deployment type considerations prior to a migration can be found here. The MA also displays some information about the source Windows vCenter Server. These included: FQDN, SSO User, SSL

Thumbprint, Port, and MA log folder. At the bottom of the MA is the Migration Steps, which will be available until the source Windows vCenter Server is shutdown. This is a helpful guide of the migration steps that need to be completed. The second purpose of the MA is copying the source Windows vCenter Server data. By default, the configuration and inventory data of the Windows vCenter Server is migrated. The option to copy historical and performance data is also available. During the migration workflow, no changes are made to the source Windows vCenter Server. This allows for an easy rollback plan. Do not close the Migration Assistant at any point during the migration workflow. Closing the MA will result in starting the entire migration process over. If everything is successful there will be a prompt at the bottom of the Migration Assistant to start the migration.

Migration Tool

Step two of the migration workflow is starting the wizard driven Migration Tool. This requires the vCenter Server Appliance 6.5 Installer. Since the identity of the source Windows vCenter Server is preserved, the migration tool needs to run on a separate Windows Server from the source. Like the VCSA 6.5 Deployment, Migration is also a two stage deployment. The Migration Tool will first deploy a new vCenter Server Appliance. The new VCSA will have a temporary IP address while the source Windows vCenter data is copied. The second stage configures the VCSA 6.5 and imports the source Windows vCenter Server data. This includes the identity of the source Windows vCenter server. The vCenter Server identity includes FQDN, IP address, UUID, Certificates, MoRef IDs, etc. As far as other solutions that communicate with vCenter Server nothing has changed. During the migration workflow, no changes are made to the source Windows vCenter Server. This allows for an easy rollback plan. Other solutions may require an upgrade, consult the VMware and any third party interoperability matrixes. Once the migration workflow is completed, login to the vSphere Client and validate your environment.

Windows External PSC 6.5 Migration to an External PSC 6.7 Appliance

This walkthrough will cover the ability to migrate a Windows Platform Services Controller (PSC) 6.5 to a PSC Appliance 6.7. The Migration process is not only a migration but also an upgrade from 6.5 to 6.7.

 

Steps 1 and 2 of the Migration Workflow will be covered in this Platform Services Controller walkthrough.

Mount the vCenter Server Appliance 6.7 ISO to the Windows Platform Services Controller 6.5 server and navigate to the migration assistant directory.

Launch the VMware-Migration Assistant.exe

Provide the Administrator@vsphere.local Single Sign-On password and press [Enter].

The migration-assistant will run pre-checks to validate the Windows Platform Services Controller is compliant and ready for the migration process.Note: Do not close the Migration Assistant window at any point or the migration process will need to be restarted.

The migration-assistant output provides an environment and settings overview of the source Windows Platform Services Controller. Also, the migrationassistant provides information about the migration steps and notification stating the Windows Platform Services Controller 6.5 will be shut down. In case of any issues during the migration process, the target Platform Services

Controller Appliance can be powered off and the Windows Platform Services

Controller 6.5 can be powered on, providing easy rollback. During the migration process, no changes are made to the source Windows Platform

Services Controller 6.5 providing easy rollback. Another warning is provided to not close the migration-assistant or the migration process will need to be restarted.

Next, connect to an available workstation or jump-box that has access to the same routable network as the Windows Platform Services Controller 6.5 to run the vCenter Server Appliance ISO from. Mount the vCenter Server Appliance ISO.

Mount the vCenter Server Appliance 6.7 ISO. You can run the Migration Tool directly from the vCenter Server Appliance ISO or copy the contents locally and run it directly from the Windows VM.

Go to the vcsa-ui-installer directory.

Go to the win32 directory.

Launch the vCenter Server Appliance 6.7 installer.

Select Migrate from the vCenter Server Appliance 6.7 installer.

The deployment workflow is a two stage process. The first stage deploys a new Platform Services Controller Appliance. The second stage configures the Appliance. Click [Next] on the Introduction screen.

Review and accept the terms of the license agreement to continue. Click on [Next].

Provide the source Windows Platform Services Controller fully qualified domain name (FQDN) or IP address and vSphere Single Sign-On password. Click on [Next].

Accept the SSL SHA1 thumbprint of the certificate by clicking on [Yes].

Provide the fully qualified domain name (FQDN) of the vSphere ESXi Host or management vCenter Server. This will be the initial deployment target for the Platform Services Controller 6.7 appliance. Provide a User Name and Password with privileges to create a VM. Click on [Next].

Accept the SSL SHA1 thumbprint of the certificate by clicking on [Yes].

Select a datacenter or VM folder to create the Platform Services Controller VM in.  Click on [Next].

Select the compute resource to deploy the Platform Services Controller VM. Click on [Next].

Provide a VM name (inventory name) for the Platform Services Controller Appliance. Enter a secure password and click on [Next].

Select a datastore from the list provided by the vSphere Host and click on [Next].

Select the Network, IP version, Temporary IP address, Subnet mask, Gateway, and DNS servers. Click on [Next]. Note: Ensure that the system name has been provided both A and PTR DNS records for forward and reverse DNS resolution.

Review the Stage 1 summary settings. Click [Finish] to start the deployment of the External Platform Services Controller 6.7.

The installer will begin to deploy the Platform Services Controller 6.7 appliance to the vSphere ESXi Host. Monitor the deployment progress.

The installer will power on the Platform Services Controller after deployment to the vSphere ESXi Host.

The deployment of the External Platform Services Controller (Stage 1) has completed. Click on [Continue] to proceed to Stage 2.Note: If [Close] is selected Stage 2 can be continued from the VMware vSphere Appliance Management Interface (https://FQDN or IP Address of vCenter Server Appliance:5480).

Stage 2 will copy the data from the source Windows 6.5 PSC to the target Platform Services Controller 6.7 appliance. Click [Next] to proceed with Stage 2.

The installer will connect to the source Windows PSC and save all parameters.

If the Windows Platform Services Controller 6.5 was joined to Active Directory, provide an account that has rights to join computers to the domain so that the target Platform Services Controller 6.7 appliance can also join the same domain.  Click on [Next].

Join the VMware Customer Experience Improvement Program (CEIP) which enables features such as, vSphere & VSAN Health.To learn more: https://www.vmware.com/solutions/trustvmware/ceip.htmlAfter a selection is made, Click [Next].

Review the Stage 2 summary settings. Validate a backup of the source Windows Platform Services Controller 6.5 has been taken. Click [Finish] to start the configuration of the Platform Services Controller 6.7 appliance.

A warning is displayed as a reminder that the source Windows Platform Services Controller 6.5 will be powered off once the network configuration is enabled on the target Platform Services Controller 6.7 appliance. Click [OK] to continue.NOTE: Once the migration process is started it can not be paused or stopped.

 

The data transfer process from the source Windows Platform Services Controller is started. This will copy the configuration data that was selected in a previous step.

Once the data has been copied from the source Windows Platform Services Controller it will be shutdown. The shutdown will allow the Platform Services Controller 6.7 appliance to assume the identity of the source Windows Platform Services Controller 6.5. The identity will include System Name (OS), IP address, UUID, Certificates, etc.

The setup of the Platform Services Controller 6.7 appliance will begin.

Once the Platform Services Controller setup is completed the data copied from the source Windows Platform Services Controller is imported.

An information message will appear about TLS settings for the new version of vSphere 6.7 as TLS 1.0 & 1.1 are now disabled by default. Click on [Close].

The configuration, setup, and data import of the Platform Services Controller 6.7 appliance has completed. Click on the link provided by the installer to launch the Getting Started Page. Click on [Close] to exit from the installer.

The Platform Services Controller web interface (https;//FQDN/psc) is now integrated within the vSphere Client (HTML5) under the Administration section.

This concludes this walkthrough on Windows Platform Services Controller 6.5

External Migration to the PSC 6.7 Appliance To learn more, visit the VMware

vSphere Blog at blogs.vmware.com/vsphere.

Windows vCenter Server 6.5 External Migration to VCSA 6.7

This walkthrough will cover the ability to migrate a Windows vCenter Server 6.5 to a vCenter Server Appliance (VCSA) 6.7. The Migration process is not only a migration but also an upgrade from vCenter Server 6.5 to 6.7.

 

A vCenter Server Migration allows the Upgrade & Migration of data into the vCenter Server Appliance (VCSA). Migration is able to retain the identity of the source vCenter Server for both embedded and external deployment topologies. All supported vCenter Server databases as also supported for migration. As a default, the migration will migrate Inventory & Configuration data and leaves data such as Historical and Performance metrics optional to import. VMware vSphere Update Manager (VUM) is included in the VCSA eliminating the need for n additional virtual machine to run VUM. The Migration Assistant also performs pre-checks to validate if the source vCenter Server is ready for migration.

A new version VCSA (upgraded) is deployed in Stage 1 and then source vCenter Server data is Migrated to the upgraded VCSA in Stage 2.It is important to understand that a vCenter Server migration is BOTH a Migration and an Upgrade.

 

Steps 4, 5, and 6 of the Migration Workflow will be covered in this vCenter Server walkthrough.

Begin by logging in your Windows vCenter Server 6.5.

Mount the vCenter Server Appliance 6.7 ISO to the Windows vCenter Server 6.5.

The migration-assistant directory on the vCenter Server Appliance 6.7 ISO can be copied locally to the Windows vCenter Server 6.5 or run directly from the ISO.In this example environment, the files were accessed directly from the vCenter Server Appliance 6.7 ISO.

Launch the Migration-Assistant application (VMware-Migration-Assistant.exe).

Provide the Administrator@vsphere.local Single Sign-On password and press [Enter].

If your Windows vCenter Server service is running as a service account you will be prompted to provide the service account credentials and press [Enter].

The migration-assistant will run pre-checks to validate your Windows vCenter Server is compliant and ready for the migration process.Note: Do not close the migration-assistant window at any point or the migration process will need to be restarted.

The migration-assistant output can be broken up into three sections. The first is "Warning". Here there will be information about extensions registered with vCenter Server. Resolutions for each warning are provided. Go through each warning and plan accordingly before proceeding.

The second section is an environment and settings overview of the source Windows vCenter Server and Migration process. Listed is the source Windows vCenter Server topology, deployment size, and database information. Notice of additional products that will be migrated is also shown. In this example, the vSphere Update Manager will also be migrated to the new VCSA 6.7. Topology will not be changed during the migration process. An embedded deployment will remain the same when migrated. Also listed is information about the Migration settings and steps.

The third and final section provides information stating the Windows vCenter Server 6.5 will be shutdown. In case of any issues during the migration, the target vCenter Server Appliance 6.7 can be powered off and the Windows vCenter Server 6.5 can be powered on. During the migration process, no changes are made to the source Windows vCenter Server 6.5 providing easy rollback. Another warning is provided to not close the migration-assistant or the process will need to be restarted.

The Windows vCenter Server will be shutdown during the migration process and separate Windows machine will be required to run the Migration Tool.Login to a Windows machine that is on a routable network to the Windows vCenter Server being migrated. Mount the vCenter Server Appliance 6.7 ISO.

Go to the vcsa-ui-installer directory.

Go to the win32 directory.

Launch the vCenter Server Appliance 6.7 installer.

Select [Migrate] from the vCenter Server Appliance 6.7 installer.

The deployment workflow is a two stage process. The first stage deploys a new vCenter Server Appliance. The second stage configures the Appliance. Click [Next] on the Introduction screen.

Review and accept the terms of the license agreement to continue. Click on [Next].

Provide the source Windows vCenter Server fully qualified domain name (FQDN) or IP address and vSphere Single Sign-On password. Click on [Next].

Accept the SSL SHA1 thumbprint by clicking on [Yes].

Provide the fully qualified domain name (FQDN) of the vSphere ESXi Host or management vCenter Server. This will be the initial deployment target for the appliance. Provide a User Name and Password with privileges to create a VM. Click on [Next].

Accept the SSL SHA1 thumbprint by clicking on [Yes].

Select a datacenter or VM folder to create the vCenter Server Appliance VM in. Click on [Next].

Select the compute resource to deploy the vCenter Server Appliance VM.  Click on [Next].

Provide a VM name (inventory name) for the vCenter Server Appliance. Enter a secure password and click on [Next].

The installer provides the option to select an [Appliance size] and [Storage size].Select the required appliance deployment size. The installer will default to the current vCenter Server size which can be increased. Optionally, select the appliance [Storage size] to increase the initial disk size for Stats, Events,

Alarms, and Tasks. Click on [Next].Note: The Appliance deployment size can not be set to a size smaller than the initial vCenter Server size. The migrationassistant will display the initial vCenter Server Deployment size.

Select a datastore from the list provided by the vSphere Host and click on [Next].

Select the Network, IP version, Temporary IP address, Subnet mask, Gateway, and DNS servers. Click on [Next]. Note: Ensure that the system name has been provided both A and PTR DNS records for forward and reverse DNS resolution.

Review the Stage 1 summary settings. Click [Finish] to start the deployment of the vCenter Server Appliance 6.7.

The installer will begin to deploy the vCenter Server Appliance to the vSphere ESXi Host. Monitor the deployment progress.

The installer will power on the vCenter Server Appliance 6.7 after deployment to the vSphere ESXi Host.

The deployment of vCenter Server Appliance (Stage 1) has completed. Click on [Continue] to proceed to Stage 2.Note: If [Close] is selected Stage 2 can be continued from the VMware vSphere Appliance Management Interface (https://FQDN or IP Address of vCenter Server Appliance:5480).

Start Stage 2 configuration of the vCenter Server Appliance 6.7 by clicking on [Next].

The pre-migration check results screen will appear. The same warnings and resolutions that were displayed in the migration-assistant will appear here. Make sure proper planning is in place to resolve these warnings after the vCenter Server Appliance configuration is completed. Click on [Close].

If the Windows vCenter Sever 6.5 was joined to Active Directory provide an account to update the object information with the vCenter Server Appliance password. Click on [Next].

Select which data to migrate from the Windows vCenter Server 6.5 to the vCenter Server Appliance 6.7. By default the vCenter Server configuration, inventory, and alarm data is migrated. Select the other options to migrate events and tasks only, migrate performance and historical data, or additionally migrate historical data in the background after deployment. Click on [Configuration and historical data (events and tasks)] to continue.

In this example environment, we will migrate historical data in the background after deployment. Click on [Next].

Review the Stage 2 summary settings. Validate a backup of the source Windows vCenter Server 6.5 has been taken. Click [Finish] to start the configuration of the vCenter Server Appliance 6.7.

A warning is displayed as a reminder that the source Windows vCenter Server 6.5 will be powered off once the network configuration is enabled on the target vCenter Server Appliance 6.7. Click [OK] to continue.NOTE: Once the migration process is started it can not be paused or stopped.

The data transfer process from the source Windows vCenter Server is started. This will copy the configuration data that was selected in a previous step to the vCenter Server Appliance.

Once the data has been copied from the source Windows vCenter Server it will be shutdown. The shutdown will allow the vCenter Server Appliance 6.7 to assume the identity of the source Windows vCenter Server. The identity will include System Name (OS), IP address, UUID, Certificates, etc.

The setup of the vCenter Server Appliance will begin.

Once the vCenter Server Appliance 6.7 setup is completed the data copied from the source Windows vCenter Server 6.5 is now imported.

An information message will appear to update DHCP and TFTP settings for the new version of Auto Deploy. This is only required if the Auto Deploy service will be used. Also information about TLS settings for the new version of vSphere 6.7 is displayed as TLS 1.0 & 1.1 are now disabled by default.Click on [Close].

The configuration, setup, and data import of the vCenter Server Appliance 6.7 has completed. Click on the links provided by the installer to launch the Getting Started Page. Click on [Close] to exit from the installer.

Login to the vCenter Server Appliance 6.7

Once logged in you can verify the installed vCenter Server version from the Summary tab of the vCenter Server view.

This concludes this walkthrough on vCenter Server 6.5 External Migration to Appliance 6.7. To learn more, visit the VMware vSphere Blog at blogs.vmware.com/vsphere.

Windows External PSC 6.0 Migration to an External PSC 6.5 Appliance

A new feature in vSphere 6.5 is the ability to migrate a Windows Platform

Services Controller (PSC) 6.0 to a PSC Appliance 6.5. The Migration process is not only a migration but also an upgrade from 6.0 to 6.5.

 

Steps 1 and 2 of the Migration Workflow will be covered in this Platform

Services Controller walkthrough.

Begin by logging in your WindowsPlatform Services Controller (PSC) 6.0.

Mount the vCenter Server Appliance 6.5 ISO to the Windows Platform Services Controller 6.0 server

Navigate to the migration-assistant directory.

Launch the VMware-Migration Assistant.exe

Provide the Administrator@vsphere.local Single Sign-On password and press [Enter].

The migration-assistant will run pre-checks to validate the Windows Platform

Services Controller is compliant and ready for the migration process.Note: Do not close the Migration Assistant window at any point or the migration process will need to be restarted.

The migration-assistant output provides an environment and settings overview of the source Windows Platform Services Controller. Also, the migrationassistant provides information about the migration steps and notification stating the Windows Platform Services Controller 6.0 will be shut down. If any issues are discovered during the migration process, the target Platform

Services Controller Appliance can be powered off and the Windows Platform

Services Controller 6.0 can be powered on, providing easy rollback. During the migration process, no changes are made to the source Windows Platform

Services Controller 6.0 providing easy rollback. Another warning is provided to not close the migration-assistant or the migration process will need to be restarted.

When the message "Waiting for migration to start..." is shown, you are ready to move to migrating the PSC.

Next, connect to an available workstation or jump-box that has access to the same routable network as the Windows Platform Services Controller 6.0 to run the vCenter Server Appliance ISO from. Mount the vCenter Server Appliance ISO.

Mount the vCenter Server Appliance 6.5 ISO. You can run the Migration Tool directly from the vCenter Server Appliance ISO or copy the contents locally and run it directly from the Windows VM.

Go to the vcsa-ui-installer directory.

Go to the win32 directory.

Launch the vCenter Server Appliance 6.5 installer.

Select Migrate from the vCenter Server Appliance 6.5 installer.

The deployment workflow is a two stage process. The first stage deploys a new Platform Services Controller Appliance. The second stage configures the Appliance. Click [Next] on the Introduction screen.

Review and accept the terms of the license agreement to continue. Click on [Next].

Provide the source Windows Platform Services Controller fully qualified domain name (FQDN) or IP address and vSphere Single Sign-On password. Click on [Next].

Accept the SSL SHA1 thumbprint of the certificate by clicking on [Yes].

Provide the fully qualified domain name (FQDN) of the vSphere ESXi Host or management vCenter Server. This will be the initial deployment target for the Platform Services Controller 6.5 appliance. Provide a User Name and Password with privileges to create a VM. Click on [Next].

Accept the SSL SHA1 thumbprint of the certificate by clicking on [Yes].

Select a datacenter or VM folder to create the Platform Services Controller VM in. Click on [Next].

Select the compute resource to deploy the Platform Services Controller VM. Click on [Next].

Provide a VM name (inventory name) for the Platform Services Controller Appliance. Enter a secure password and click on [Next].

Select a datastore from the list provided by the vSphere Host and click on [Next].

Select the Network, IP version, Temporary IP address, Subnet mask, Gateway, and DNS servers. Click on [Next]. Note: Ensure that the system name has been provided both A and PTR DNS records for forward and reverse DNS resolution.

Review the Stage 1 summary settings. Click [Finish] to start the deployment of the External Platform Services Controller 6.5.

The installer will begin to deploy the Platform Services Controller 6.5 appliance to the vSphere ESXi Host. Monitor the deployment progress.

The installer will power on the Platform Services Controller after deployment to the vSphere ESXi Host.

The deployment of the External Platform Services Controller (Stage 1) has completed. Click on [Continue] to proceed to Stage 2.Note: If [Close] is selected Stage 2 can be continued from the VMware vSphere Appliance Management Interface (https://FQDN or IP Address of vCenter Server Appliance:5480).

Stage 2 will copy the data from the source Windows 6.0 PSC to the target Platform Services Controller 6.5 appliance. Click [Next] to proceed with Stage 2.

The installer will connect to the source Windows PSC and save all parameters.

If the Windows Platform Services Controller 6.0 was joined to Active Directory, provide an account that has rights to join computers to the domain so that the target Platform Services Controller 6.5 appliance can also join the same domain.  Click on [Next].

Join the VMware Customer Experience Improvement Program (CEIP) which enables features such as, vSphere & VSAN Health.To learn more: https://www.vmware.com/solutions/trustvmware/ceip.htmlAfter a selection is made, Click [Next].

 

Review the Stage 2 summary settings. Validate a backup of the source Windows Platform Services Controller 6.0 has been taken. Click [Finish] to start the configuration of the Platform Services Controller 6.5 appliance.

A warning is displayed as a reminder that the source Windows Platform

Services Controller 6.0 will be powered off once the network configuration is enabled on the target Platform Services Controller 6.5 appliance. Click [OK] to continue.NOTE: Once the migration process is started it can not be paused or stopped.

The data transfer process from the source Windows Platform Services Controller is started. This will copy the configuration data that was selected in a previous step.

Once the data has been copied from the source Windows Platform Services

Controller it will be shutdown. The shutdown will allow the Platform Services

Controller 6.5 appliance to assume the identity of the source Windows

Platform Services Controller 6.0. The identity will include System Name (OS),

IP address, UUID, Certificates, etc.

The setup of the Platform Services Controller 6.5 appliance will begin.

Once the Platform Services Controller setup is completed the data copied from the source Windows Platform Services Controller is imported.

The configuration, setup, and data import of the Platform Services Controller 6.5 appliance has completed. Click on the link provided by the installer to launch the Getting Started Page. Click on [Close] to exit from the installer.

When the Getting Started page is launched you will notice that the PSC management interface is accessible from this page.

This concludes this walkthrough on Windows Platform Services Controller 6.0 External Migration to the PSC 6.5 Appliance. To learn more, visit the VMware vSphere Blog at blogs.vmware.com/vsphere.

Windows vCenter Server 6.5 Embedded Migration to VCSA 6.7

This walkthrough will cover the ability to migrate a Windows Embedded vCenter Server 6.5 to a VCSA 6.7. The Migration process is not only a migration but also an upgrade from 6.5 to 6.7.

A vCenter Server Migration allows the Upgrade & Migration of data into the vCenter Server Appliance (VCSA). Migration is able to retain the identity of the source vCenter Server for both embedded and external deployment topologies. All supported vCenter Server databases as also supported for migration. As a default, the migration will migrate Inventory & Configuration data and leaves data such as Historical and Performance metrics optional to import. VMware vSphere Update Manager (VUM) is included in the VCSA eliminating the need for n additional virtual machine to run VUM. The

Migration Assistant also performs pre-checks to validate if the source vCenter

Server is ready for migration.

A new version VCSA (upgraded) is deployed in Stage 1 and then source vCenter Server data is Migrated to the upgraded VCSA in Stage 2.It is important to understand that a vCenter Server migration is BOTH a Migration and an Upgrade.

Begin by logging in your Windows vCenter Server 6.5

Mount the vCenter Server Appliance 6.7 ISO to the Windows vCenter Server 6.5.

Browse to the migration-assistant directory from the vCenter Server Appliance 6.7 ISO

Launch the VMware-Migration-Assistant application.

Provide the Administrator@vsphere.local Single Sign-On password and press [Enter].

The migration-assistant will run pre-checks to validate your Windows vCenter Server is compliant and ready for the migration process.Note: Do not close the migration-assistant window at any point or the migration process will need to be restarted.

The section shown is an environment and settings overview of the source Windows vCenter Server and Migration process. Listed is the source Windows vCenter Server topology, deployment size, and database information. Topology will not be changed during the migration process. An embedded deployment will remain the same when migrated. Also listed is information about the Migration settings and steps.

The next section provides information stating the Windows vCenter Server 6.5 will be shutdown. In case of any issues during the migration, the target vCenter

Server Appliance can be powered off and the Windows vCenter Server 6.5 can be powered on. During the migration process, no changes are made to the source Windows vCenter Server 6.5 providing easy rollback. Another warning is provided to not close the migration-assistant or the process will need to be restarted.

Since the Windows vCenter Server will be shutdown during the migration process a separate Windows VM will be required to run the Migration Tool. Login to a separate Windows VM that is on a routable network to the Windows vCenter Server being migrated.

Mount the vCenter Server Appliance 6.7 ISO. You can run the Migration Tool directly from the vCenter Server Appliance ISO or copy the contents locally and run it directly from the Windows VM.

Go to the vcsa-ui-installer directory.

Go to the win32 directory.

Launch the vCenter Server Appliance 6.7 installer.

Select Migrate from the vCenter Server Appliance 6.7 installer.

The deployment workflow is a two stage process. The first stage deploys a new vCenter Server Appliance. The second stage configures the Appliance. Click [Next] on the Introduction screen.

Review and accept the terms of the license agreement to continue. Click on [Next].

Provide the source Windows vCenter Server fully qualified domain name (FQDN) or IP address and vSphere Single Sign-On password. Click on [Next].

Accept the SSL SHA1 thumbprint by clicking on [Yes].

Provide the fully qualified domain name (FQDN) of the vSphere ESXi Host or management vCenter Server. This will be the initial deployment target for the appliance. Provide a User Name and Password with privileges to create a VM. Click on [Next]. 

Accept the SSL SHA1 thumbprint by clicking on [Yes].

Select a datacenter or VM folder to create the VCSA 6.7 in.  Click on [Next].

Select the compute resource to deploy the VCSA 6.7 in.  Click on [Next].

Provide a VM name (inventory name) for the vCenter Server Appliance. Enter a secure password and click on [Next].

The installer provides the option to select an [Appliance size] and [Storage size]. Select the required appliance deployment size. The installer will default to the current vCenter Server size which can be increased. Optionally, select the appliance [Storage size] to increase the initial disk size for Stats, Events,

Alarms, and Tasks. Click on [Next].Note: The Appliance deployment size can not be set to a size smaller than the initial vCenter Server size. The migrationassistant will display the initial vCenter Server Deployment size.

Select a datastore from the list provided by the vSphere Host and click on [Next].

Select the Network, IP version, Temporary IP address, Subnet mask, Gateway, and DNS servers. Click on [Next]. Note: Ensure that the system name has been provided both A and PTR DNS records for forward and reverse DNS resolution.

Review the Stage 1 summary settings. Click [Finish] to start the deployment of the VCSA 6.7 with Embedded Platform Services Controller.

The installer will begin to deploy the VCSA 6.7 appliance to the vSphere ESXi Host. Monitor the deployment progress.

The installer will power on the VCSA 6.7 after deployment to the vSphere ESXi Host.

The deployment of vCenter Server Appliance with an Embedded Platform

Services Controller (Stage 1) has completed. Click on [Continue] to proceed to

Stage 2.Note: If [Close] is selected Stage 2 can be continued from the VMware vSphere Appliance Management Interface (https://FQDN or IP Address of vCenter Server Appliance:5480).

Start Stage 2 configuration of the vCenter Server Appliance 6.7 with an Embedded Platform Services Controller by clicking on [Next].

Connect to the source vCenter Server by providing the Windows Server FQDN name and the Single Sign-On password. Click [Next] to continue.

Accept the certificate, click [Next] to continue.

The installer will connect to the source Windows vCenter Server and save all parameters.

If the Windows vCenter Sever 6.5 was joined to Active Directory provide an account to update the object information with the vCenter Server Appliance password. Click on [Next].

Select which data to migrate from the Windows vCenter Server 6.5 to the vCenter Server Appliance 6.7. By default the vCenter Server configuration, inventory, and alarm data is migrated. Select the other options to migrate events and tasks only or additionally migrate performance and historical data as well. Click on [Next].

Join the VMware Customer Experience Improvement Program (CEIP) which enables features such as, vSphere & VSAN Health.To learn more: https://www.vmware.com/solutions/trustvmware/ceip.htmlAfter a selection is made, Click [Next].

Review the Stage 2 summary settings. Validate a backup of the source Windows vCenter Server 6.5 has been taken. Click [Finish] to start the configuration of the VCSA 6.7 with Embedded Platform Services Controller.

A warning is displayed as a reminder that the source Windows vCenter Server 6.5 will be powered off once the network configuration is enabled on the target VCSA 6.7 appliance. Click [OK] to continue.NOTE: Once the migration process is started it can not be paused or stopped.

The data transfer process from the source Windows vCenter Server 6.5 is started. This will copy the configuration data that was selected in a previous step.

Once the data has been copied from the source Windows vCenter Server 6.5 it will be shutdown. The shutdown will allow the vCenter Server Appliance 6.7 to assume the identity of the source Windows vCenter Server. The identity will include System Name (OS), IP address, UUID, Certificates, etc.

The setup of the vCenter Server Appliance 6.7 will begin.

Once the vCenter Server Appliance setup is completed the data copied from the source Windows vCenter Server is now imported.

An informational message will appear to update DHCP and TFTP settings for the new version of Auto Deploy. This is only required if the Auto Deploy service will be used. Also information about TLS settings for the new version of vSphere 6.7 is displayed as TLS 1.0 & 1.1 are now disabled by default.Click on [Close].

The configuration, setup, and data import of the vCenter Server Appliance 6.7 has completed. Click on the links provided by the installer to launch the Getting Started Page. Click on [Close] to exit from the installer.

From the Getting Started Page. Click on [Launch vSphere Client (HTML5)] to continue.

Login to the vCenter Server Appliance 6.7

Once logged in you can verify the installed vCenter Server version from the Summary tab of the vCenter Server view.

This concludes this walkthrough on vCenter Server 6.5 Embedded Migration to Appliance 6.7. To learn more, visit the VMware vSphere Blog at blogs.vmware.com/vsphere.

Windows vCenter Server 6.0 External Migration to VCSA 6.5

A new feature in vSphere 6.5 is the ability to migrate a Windows vCenter Server 5.5 or 6.0 to a vCenter Server Appliance 6.5. The Migration process is not only a migration but also an upgrade from vCenter Server 5.5 or 6.0 to 6.5.

A vCenter Server Migration allows the Upgrade & Migration of data into the vCenter Server Appliance (VCSA). Migration is able to retain the identity of the source vCenter Server for both embedded and external deployment topologies. All supported vCenter Server databases as also supported for migration. As a default, the migration will migrate Inventory & Configuration data and leaves data such as Historical and Performance metrics optional to import. VMware vSphere Update Manager (VUM) is included in the VCSA eliminating the need for n additional virtual machine to run VUM. The Migration Assistant also performs pre-checks to validate if the source vCenter Server is ready for migration.

A new version VCSA (upgraded) is deployed in Stage 1 and then source vCenter Server data is Migrated to the upgraded VCSA in Stage 2.It is important to understand that a vCenter Server migration is BOTH a Migration and an Upgrade.

 

Steps 4, 5, and 6 of the Migration Workflow will be covered in this vCenter Server walkthrough.

Begin by logging in your Windows vCenter Server 6.0.

Mount the vCenter Server Appliance 6.5 ISO to the Windows vCenter Server 6.0.

The migration-assistant directory on the vCenter Server Appliance 6.5 ISO can be copied locally to the Windows vCenter Server 6.0 or run directly from the ISO.In this example environment, the files were accessed directly from the vCenter Server Appliance 6.5 ISO.

Launch the Migration-Assistant application (VMware-Migration-Assistant.exe).

Provide the Administrator@vsphere.local Single Sign-On password and press [Enter].

If your Windows vCenter Server service is running as a service account you will be prompted to provide the service account credentials and press [Enter].

The migration-assistant will run pre-checks to validate your Windows vCenter

Server is compliant and ready for the migration process.Note: Do not close the migration-assistant window at any point or the migration process will need to be restarted.

The migration-assistant output can be broken up into sections. This section is an environment and settings overview of the source Windows vCenter Server and Migration process. Listed is the source Windows vCenter Server topology, deployment size, and database information. Notice of additional products that will be migrated is also shown if applicable. Topology will not be changed during the migration process. An embedded deployment will remain the same when migrated. Also listed is information about the Migration settings and steps.

The next section provides information stating the Windows vCenter Server 6.0 will be shutdown. In case of any issues during the migration, the target vCenter

Server Appliance 6.5 can be powered off and the Windows vCenter Server 6.0 can be powered back on and re-joined to the domain. During the migration process, no changes are made to the source Windows vCenter Server 6.0 providing easy rollback. Another warning is provided to not close the migration-assistant or the process will need to be restarted.

Since the Windows vCenter Server will be shutdown during the migration process a separate Windows VM will be required to run the Migration Tool.Login to a separate Windows VM that is on a routable network to the Windows vCenter Server being migrated.

Mount the vCenter Server Appliance 6.5 ISO.

Go to the vcsa-ui-installer directory.

Go to the win32 directory.

Launch the vCenter Server Appliance 6.5 installer.

Select [Migrate] from the vCenter Server Appliance 6.5 installer.

The deployment workflow is a two stage process. The first stage deploys a new vCenter Server Appliance. The second stage configures the Appliance. Click [Next] on the Introduction screen.

Review and accept the terms of the license agreement to continue. Click on [Next].

Provide the source Windows vCenter Server 6.0 fully qualified domain name (FQDN) or IP address and vSphere Single Sign-On password. Click on [Next].

Accept the SSL SHA1 thumbprint by clicking on [Yes].

Provide the fully qualified domain name (FQDN) of the vSphere ESXi Host or management vCenter Server. This will be the initial deployment target for the appliance. Provide a User Name and Password with privileges to create a VM. Click on [Next].

Accept the SSL SHA1 thumbprint by clicking on [Yes].

Select a datacenter or VM folder to create the vCenter Server Appliance VM in. Click on [Next].

Select the compute resource to deploy the vCenter Server Appliance VM. Click on [Next].

Provide a VM name (inventory name) for the vCenter Server Appliance. Enter a secure password and click on [Next].

The installer provides the option to select an [Appliance size] and [Storage size].Select the required appliance deployment size. The installer will default to the current vCenter Server size which can be increased. Optionally, select the appliance [Storage size] to increase the initial disk size for Stats, Events,

Alarms, and Tasks. Click on [Next].Note: The Appliance deployment size can not be set to a size smaller than the initial vCenter Server size. The migrationassistant will display the initial vCenter Server Deployment size.

Select a datastore from the list provided by the vSphere Host and click on [Next].

Select the Network, IP version, Temporary IP address, Subnet mask, Gateway, and DNS servers. Click on [Next]. Note: Ensure that the system name has been provided both A and PTR DNS records for forward and reverse DNS resolution.

Review the Stage 1 summary settings. Click [Finish] to start the deployment of the vCenter Server Appliance 6.5.

The installer will begin to deploy the vCenter Server Appliance to the vSphere ESXi Host. Monitor the deployment progress.

The installer will power on the vCenter Server Appliance 6.5 after deployment to the vSphere ESXi Host.

The deployment of vCenter Server Appliance (Stage 1) has completed. Click on [Continue] to proceed to Stage 2.Note: If [Close] is selected Stage 2 can be continued from the VMware vSphere Appliance Management Interface (https://FQDN or IP Address of vCenter Server Appliance:5480).

Start Stage 2 configuration of the vCenter Server Appliance 6.5 by clicking on [Next].

Pre-migration checks will run before continuing.

If the Windows vCenter Sever 6.0 was joined to Active Directory provide an account to update the object information with the vCenter Server Appliance password. Click on [Next].

Select which data to migrate from the Windows vCenter Server 6.0 to the vCenter Server Appliance 6.5. By default the vCenter Server configuration, inventory, and alarm data is migrated. Select the other options to migrate events and tasks only, or migrate events and tasks & performance metrics.Click on [Configuration and historical data (events and tasks)] to continue.

Review the Stage 2 summary settings. Validate a backup of the source Windows vCenter Server 6.0 has been taken. Click [Finish] to start the configuration of the vCenter Server Appliance 6.5.

A warning is displayed as a reminder that the source Windows vCenter Server 6.0 will be powered off once the network configuration is enabled on the target vCenter Server Appliance 6.5. Click [OK] to continue.NOTE: Once the migration process is started it can not be paused or stopped.

The data transfer process from the source Windows vCenter Server is started. This will copy the configuration data that was selected in a previous step to the vCenter Server Appliance.

Once the data has been copied from the source Windows vCenter Server it will be shutdown. The shutdown will allow the vCenter Server Appliance 6.5 to assume the identity of the source Windows vCenter Server. The identity will include System Name (OS), IP address, UUID, Certificates, etc.

The setup of the vCenter Server Appliance will begin.

Once the vCenter Server Appliance 6.5 setup is completed the data copied from the source Windows vCenter Server 6.0 is now imported.

The configuration, setup, and data import of the vCenter Server Appliance 6.5 has completed. Click on the links provided by the installer to launch the Getting Started Page. Click on [Close] to exit from the installer.

The installer will load the VCSA Getting Started page. Choose a vSphere Client to login.

Login to the vCenter Server Appliance 6.5

Once logged in you can verify the installed vCenter Server version from the Summary tab of the vCenter Server view.

This concludes this walkthrough on vCenter Server 6.0 External Migration to VCSA 6.5. To learn more, visit the VMware vSphere Blog at blogs.vmware.com/vsphere.

Migration from vCenter Server 6.0 Embedded to VCSA 6.5

This guide will show how to migrate a Windows vCenter Server and the Platform Services Controller 6.0 components on a single virtual machine to a vCenter Server Appliance 6.5.

 

Video: PSC reconfiguration during migration

Learn about vCenter Server upgrade and migration, and the use of PSC repointing & reconfiguring during this process, using an innovative white board format.

 

Video: Topology Considerations

This video goes over various topics related to vCenter Server topology. It covers upgrade from vSphere 5.5 to vSphere 6.5, Enhanced Linked Mode, and SSO Domain consolidation, all using an innovative white board format.

 

Filter Tags