vSphere Migration vCenter Server 6.0 ESXi 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
vSphere Migration You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2016 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc.
Contents About vSphere Migration 5 1 System Requirements for Migrating vCenter Server Deployments to vCenter Server Appliance Deployments 7 2 vCenter Server Appliance Requirements 9 vCenter Server Appliance Hardware Requirements 9 vCenter Server Appliance Storage Requirements 10 Software Included in the vCenter Server Appliance 11 vCenter Server Appliance Software Requirements 11 vCenter Server Appliance Database Requirements 11 vSphere Web Client Software Requirements 11 Required Ports for vCenter Se
vSphere Migration 8 After Migrating vCenter Server 51 Check vCenter Server Instance Upgrade or Migration 51 Verify Your vCenter Server Appliance Migration Is Successful 51 Log in to vCenter Server Appliance by Using the vSphere Web Client 52 9 Troubleshooting 53 View Migration Assistant Logs and Status Files 53 Index 4 55 VMware, Inc.
About vSphere Migration ® The vSphere Migration guide provides information about migrating VMware vCenter Server Appliance. vCenter Server to To move to the current version of vSphere by performing a fresh installation that does not preserve existing configurations, see the vSphere Installation and Setup documentation. To upgrade your vSphere environment, see vSphere Upgrade. For information about Migration Assistant and answers to frequently asked questions, see http://kb.vmware.com/kb/2146439.
vSphere Migration 6 VMware, Inc.
System Requirements for Migrating vCenter Server Deployments to vCenter Server Appliance Deployments 1 Your source and target systems must meet specific software and hardware requirements before you can migrate a vCenter Server or a vCenter Single Sign-On deployment to a vCenter Server Appliance or Platform Services Controller appliance. Source System n Synchronize the clocks on all machines running the source vCenter Server services. See “Synchronizing Clocks on the vSphere Network,” on page 24.
vSphere Migration Target System 8 n Your target system must meet specific software and hardware requirements for vCenter Server Appliance. See Chapter 2, “vCenter Server Appliance Requirements,” on page 9. n When you use Fully Qualified Domain Names, make sure that the machine you use for deploying the vCenter Server Appliance and the target ESXi host or vCenter Server instance are on the same DNS server.
vCenter Server Appliance Requirements 2 You can migrate the vCenter Server Appliance on an ESXi host 5.0 or later. Your system must also meet specific software and hardware requirements. When you use Fully Qualified Domain Names, make sure that the machine you use for deploying the vCenter Server Appliance and the ESXi host are on the same DNS server. Before you migrate the vCenter Server to vCenter Server Appliance, synchronize the clocks of all virtual machines on the vSphere network.
vSphere Migration Table 2‑1.
Chapter 2 vCenter Server Appliance Requirements Software Included in the vCenter Server Appliance The vCenter Server Appliance is a preconfigured Linux-based virtual machine optimized for running vCenter Server and associated services. The vCenter Server Appliance package contains the following software: n SUSE Linux Enterprise Server 11 Update 3 for VMware, 64-bit edition n PostgreSQL n vCenter Server 6.0 and vCenter Server 6.0 components.
vSphere Migration Required Ports for vCenter Server and Platform Services Controller The vCenter Server system both on Windows and in the appliance, must be able to send data to every managed host and receive data from the vSphere Web Client and the Platform Services Controller services. To enable migration and provisioning activities between managed hosts, the source and destination hosts must be able to receive data from each other.
Chapter 2 vCenter Server Appliance Requirements Table 2‑4. Ports Required for Communication Between Components (Continued) Used for Node-toNode Communication Port Protocol Description Required for 88 TCP Active Directory server. Windows installations and appliance deployments of Platform Services Controller No 389 TCP/UDP This port must be open on the local and all remote instances of vCenter Server. This is the LDAP port number for the Directory Services for the vCenter Server group.
vSphere Migration Table 2‑4. Ports Required for Communication Between Components (Continued) Used for Node-toNode Communication Port Protocol Description Required for 636 TCP vCenter Single Sign-On LDAPS Windows installations and appliance deployments of Platform Services Controller vCenter Server to Platform Services Controller 902 TCP/UDP The default port that the vCenter Server system uses to send data to managed hosts.
Chapter 2 vCenter Server Appliance Requirements Table 2‑4. Ports Required for Communication Between Components (Continued) Used for Node-toNode Communication Port Protocol Description Required for 5480 TCP vCenter Server Appliance Web user interface (HTTPS) Appliance deployments of n vCenter Server n Platform Services Controller No 6500 TCP/UDP ESXi Dump Collector port Important You can change this port number during the vCenter Server installations on Windows.
vSphere Migration To configure the vCenter Server system to use a different port to receive vSphere Web Client data, see the vCenter Server and Host Management documentation. For more information about firewall configuration, see the vSphere Security documentation. 16 VMware, Inc.
Pre-migration Checks 3 When you migrate vCenter Server or vCenter Single Sign-On on Windows to an appliance, the installer does a pre-check, for example, to verify that enough space is available on the source machine, and verifies that the external database, if any, can be successfully accessed. Source Environment Checks When you migrate vCenter Single Sign-On (version 5.5), the vCenter Single Sign-On is included as part of the Platform Services Controller.
vSphere Migration 18 n Minimum processor requirements n Minimum memory requirements n Minimum disk space requirements n Permissions on the selected install and data directory n Internal and external port availability n Administrator privileges on the target host n Any credentials that you enter VMware, Inc.
Known Limitations 4 The current release of Migration Assistant has several known limitations. The following list contains features or actions that are currently not supported: vSphere Update Manager is not migrated. If you use Update Manager in your environment, there are more steps you must perform to manually move Update Manager to a new destination machine. See “Moving Update Manager to a New Host Machine When Migrating vCenter Server to vCenter Server Appliance,” on page 21.
vSphere Migration 20 VMware, Inc.
Preparing for Migration 5 Before beginning to migrate any type of vCenter Server deployment to an appliance, you must complete the preparation tasks. Preparation tasks:.
vSphere Migration vCenter Server Deployment Uses Embedded Update Manager If Update Manager, vCenter Server, and vCenter Single Sign-On 5.5 run on the same machine, or if Update Manager 5.5 and vCenter Single Sign-On 5.5 run on the same machine, perform the following steps: 1 “Move the Update Manager Server and Database to a New Host Machine,” on page 22. 2 Migrate vCenter Server 5.5 or vCenter Single Sign-On to an appliance.
Chapter 5 Preparing for Migration 4 On the destination machine, create DSN to point to the Update Manager database. For more information about how to create DSN, see Installing and Administering VMware vSphere Update Manager. 5 On the source machine, in the Start Menu, either in the Run Box or the Search box, type regedit and press Enter. The Microsoft Registry Editor opens. 6 In the Microsoft Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware Update Manager.
vSphere Migration 8 On the source machine, copy the data folder of Update Manager. The default directory where Update Manager data is stored is C:\ProgramData\VMware\VMware Update Manager\Data. For a custom location of the Update Manager data folder, see the PatchStore registry value. 9 If you used a custom SslVerifyDownloadCertificate registry value on your Update Manager source machine, make the same customization on the destination machine. 10 If you modified the jetty-vum-ssl.xml or vci-integrity.
Chapter 5 Preparing for Migration 5 Click Add. 6 In the Add NTP Server dialog box, enter the IP address or fully qualified domain name of the NTP server to synchronize with. 7 Click OK. The host time synchronizes with the NTP server. Preparing vCenter Server Certificates for Migration You must verify that your vCenter Server certificates are prepared before you start the migration process. Certificate Files Location The vCenter Server certificate files are located at %ProgramData%\VMware\VMware Virt
vSphere Migration To ensure your database is prepared for migration: n Verify that passwords are current and not set to expire soon. n For vCenter Server 5.5, run the cleanup scripts to remove any unnecessary data in the vCenter Server database using the steps for your database. For details see: n “Prepare an Oracle Database for Migration,” on page 26, n “Prepare a Microsoft SQL Server Database for Migration,” on page 27 n Verify that you have backed up your database.
Chapter 5 Preparing for Migration 4 Verify that the JDBC driver file is included in the CLASSPATH variable. 5 Verify that permissions are set correctly. 6 Either assign the DBA role or grant the required permissions to the user. 7 For vCenter Server 5.5, run the cleanup script. a Locate the cleanup_orphaned_data_Oracle.sql script in the ISO image and copy it to the Oracle server. b Log in to a SQL*Plus session with the vCenter Server database account. c Run the cleanup script.
vSphere Migration 6 For vCenter Server 5.5, run the cleanup script. a Locate the cleanup_orphaned_data_MSSQL.sql script in the ISO image and copy it to the Microsoft SQL server. b Log in to your database. c n For Microsoft SQL Server Express, open a command prompt. n For Microsoft SQL Server, log in to a Microsoft SQL Server Management Studio session as the vCenter Server database user. Run the cleanup script. For Microsoft SQL Server Express, run: sqlcmd -E -S localhost\VIM_SQLEXP -d VIM_VCDB -i
Chapter 5 Preparing for Migration Host Upgrades and Certificates If you upgrade an ESXi host to ESXi 6.0 or later, the upgrade process replaces the self-signed (thumbprint) certificates with VMCA-signed certificates. If the ESXi host uses custom certificates, the upgrade process retains those certificates even if those certificates are expired or invalid. If you decide not to upgrade your hosts to ESXi 6.
vSphere Migration 4 Change the value of vpxd.certmgmt.mode to custom if you intend to manage your own certificates, and to thumbprint if you temporarily want to use thumbprint mode, and click OK. 5 Restart the vCenter Server service. Install the Client Integration Plug-In You must install the Client Integration Plug-in before you migrate to the vCenter Server Appliance. Prerequisites “Download the vCenter Server Appliance Installer,” on page 36.
Chapter 5 Preparing for Migration Table 5‑1. Information Required for Migrating vCenter Server from Windows to vCenter Server Appliance Required Information Required source vCenter Server or vCenter Single SignOn migration data Default Value Your Entry vCenter Server or vCenter Single Sign-On IP address or FQDN vCenter Single Sign-On administrator user name administrator@vsphere.
vSphere Migration Table 5‑1. Information Required for Migrating vCenter Server from Windows to vCenter Server Appliance (Continued) Required Information Default Value vCenter Server Appliance size. The options vary depending on the size of your vSphere environment.
Chapter 5 Preparing for Migration Table 5‑1. Information Required for Migrating vCenter Server from Windows to vCenter Server Appliance (Continued) Required Information Default Value Enable or disable SSH Disabled by default Migration Assistant port number 9123 or the port number that is shown in the Migration Assistant console VMware, Inc.
vSphere Migration 34 VMware, Inc.
Migration of vCenter Server with an Embedded vCenter Single Sign-On to an Appliance 6 You can migrate a vCenter Server instance with an embedded vCenter Single Sign-On to a vCenter Server Appliance with an embedded Platform Services Controller appliance. When you migrate from vCenter Server with an embedded vCenter Single Sign-On (version 5.5) on Windows to vCenter Server Appliance with an embedded Platform Services Controller appliance, the entire installation is migrated at the same time.
vSphere Migration n Copies the required files to the new vCenter Server Appliance. n Runs the migration process on the new vCenter Server Appliance as specified in the Summary. n Imports and updates the files and settings of the source vCenter Server installation to the new vCenter Server Appliance. Prerequisites Assemble the “Required Information for Migrating vCenter Server and vCenter Single Sign-On from Windows to an Appliance,” on page 30.
Chapter 6 Migration of vCenter Server with an Embedded vCenter Single Sign-On to an Appliance 2 Run pre-checks on the source. 3 Report errors that must be addressed before starting the migration. 4 Provide information for the next steps in the migration process. Important Ensure that the Migration Assistant window remains open during the migration process. Closing the Migration Assistant causes the migration process to stop.
vSphere Migration n If you plan to assign a DHCP IP address in the temporary network settings of the new appliance, verify that the ESXi host on which you want to deploy the new appliance is in the same network as the ESXi host on which the existing vCenter Server runs.
Chapter 6 Migration of vCenter Server with an Embedded vCenter Single Sign-On to an Appliance 10 On the Connect to source page, enter the details for the source vCenter Server instance, and click Next. a Enter the IP address or FQDN. b Enter the user name and password of a user who has administrative privileges on the vCenter Server instance, for example, the administrator@vsphere.local user. c Enter the Migration Assistant Port you received in the Migration Assistant instructions.
vSphere Migration Option Action Choose a network Select the network to which to connect the new appliance temporarily. Verify that the temporary network provides connectivity between the source vCenter Server and the target vCenter Server Appliance. The networks displayed in the drop-down menu depend on the network settings of the target server.
Migration of vCenter Server with an External vCenter Single Sign-On to an Appliance 7 You can migrate a vCenter Server with an external vCenter Single Sign-On to an appliance. When you migrate from vCenter Server with an external vCenter Single Sign-On (version 5.5) on Windows to vCenter Server Appliance with an external Platform Services Controller appliance, you migrate in two steps. 1 First you migrate the vCenter Single Sign-On instance from Windows to an appliance.
vSphere Migration Figure 7‑1. vCenter Server 5.5 with External vCenter Single Sign-On Before and After Migration External vCenter Single Sign-On 5.5 External Platform Services Controller 6.0 vCenter Single Sign-On Platform Services Controller Windows OS Appliance vCenter Server 5.5 vCenter Inventory Service vSphere Web Client vCenter Server Appliance 6.
Chapter 7 Migration of vCenter Server with an External vCenter Single Sign-On to an Appliance 3 Migrate an External vCenter Single Sign-On instance to a Platform Services Controller appliance on page 44 You can use the Client Integration Plug-In to migrate an external vCenter Single Sign-On instance to a Platform Services Controller appliance. 4 Migrate vCenter Server to an Appliance on page 47 You can use the Client Integration Plug-In to migrate a vCenter Server 5.5.x to a vCenter Server Appliance 6.
vSphere Migration Procedure 1 Navigate to the migration-assistant directory of the vCenter Server Appliance installer package and copy the migration-assistant folder to the source vCenter Server or vCenter Single Sign-On instance. 2 Start Migration Assistant n Double-click VMware-Migration-Assistant.exe n From the command line run VMware-Migration-Assistant.exe --help to launch Migration Assistant and display the help options.
Chapter 7 Migration of vCenter Server with an External vCenter Single Sign-On to an Appliance 4 Review the Introduction page to understand the migration process and click Next. 5 Read and accept the license agreement, and click Next. 6 Connect to the target server on which you want to deploy the Platform Services Controller. Option Steps You can connect to an ESXi host on which to deploy the appliance.
vSphere Migration 14 From the list of available datastores, select the location where all the virtual machine configuration files and virtual disks will be stored and, optionally, enable thin provisioning by selecting Enable Thin Disk Mode. 15 On the Set up temporary network page, set up the network settings. The IP address or the FQDN of the appliance is used as a system name. It is recommended to use an FQDN.
Chapter 7 Migration of vCenter Server with an External vCenter Single Sign-On to an Appliance Migrate vCenter Server to an Appliance You can use the Client Integration Plug-In to migrate a vCenter Server 5.5.x to a vCenter Server Appliance 6.
vSphere Migration 6 Connect to the target server on which you want to deploy the vCenter Server Appliance. Option Steps You can connect to an ESXi host on which to deploy the appliance. 1 2 3 4 5 You can connect to a vCenter Server instance and browse the inventory to select an ESXi host or DRS cluster on which to deploy the appliance. If you select a DRS cluster, verify that the cluster is not set to Fully Automated DRS for the duration of the deployment.
Chapter 7 Migration of vCenter Server with an External vCenter Single Sign-On to an Appliance 13 On the Select appliance size page of the wizard, select the vCenter Server Appliance size for the vSphere inventory size and click Next. Option Description Tiny (up to 10 hosts, 100 VMs) Deploys an appliance with 2 CPUs, 8 GB of memory, and 120 GB of disk space. Small (up to 100 hosts, 1,000 VMs) Deploys an appliance with 4 CPUs, 16 GB of memory, and 150 GB of disk space.
vSphere Migration 17 On the Ready to complete page, review the settings for the vCenter Server Appliance migration and click Finish to complete the process. The source vCenter Server is migrated from Windows to an appliance. The source vCenter Server is powered off and the new appliance starts. What to do next Verify that your migration to an appliance was successful. For verification steps, see “Verify Your vCenter Server Appliance Migration Is Successful,” on page 51. 50 VMware, Inc.
After Migrating vCenter Server 8 After you migrate to vCenter Server Appliance, consider the post-migration options and requirements. n You can review the migration logs. See “View Migration Assistant Logs and Status Files,” on page 53. n Complete any component reconfigurations that might be required for changes during upgrade. n Verify that you understand the authentication process and identify your identity sources.
vSphere Migration Procedure 1 Verify that the IP address is correct. 2 Verify that the Active Directory registration has not changed. 3 Verify the Network registration is correct. 4 Verify the Domain is correct. 5 Verify the certificates are valid. 6 Verify the inventory data is correctly migrated. a Review the events history. b Review the performance charts. c Review the users, permissions, and roles.
9 Troubleshooting The vSphere Migration troubleshooting topics provide solutions to problems that you might encounter during the vCenter Server migration process. For information about rolling back a migration, see http://kb.vmware.com/kb/2146453 View Migration Assistant Logs and Status Files You can use Migration Assistant log files and status files to troubleshoot migration failures. If the migration fails, Migration Assistant generates a log file bundle on your desktop.
vSphere Migration Table 9‑2. Log and status files locations on the target vCenter Server Appliance or Platform Services Controller (Continued) File Location Export log files /var/log/vmware/upgrade/UpgradeRunner.log /var/log/vmware/upgrade/upgrade-export.log First boot component log files /var/log/firstboot/ComponentNamefirstboot.py_##_stdout.log /var/log/firstboot/ComponentNamefirstboot.py_##_stderr.log Import log files /var/log/vmware/upgrade/UpgradeRunner.
Index C certificates, host upgrades 29 check source platform 51 Client Integration plug-in, installing 30 clients, firewall 12 configuring ports 12 custom certificates 29 D database requirements, vCenter Server Appliance 11 database,prepare for migration 25 E esxi custom certificate mode 29 esxi thumbprint certificate mode 29 F firewall 12 G glossary 5 GUI migration embedded use case 41 overview 35 H hardware requirements, vCenter Server Appliance 9 host upgrades and certificates 29 hosts firewall 12
vSphere Migration tiny environment, required storage space 10 troubleshooting vCenter Server migration 53 vCenter Server Appliance migration 53 V vCenter Server logging in to 52 migration 53 ports 12 post-migration considerations 51 vCenter Server Appliance .
