6.0.2
Table Of Contents
- vSphere Migration
- Contents
- About vSphere Migration
- System Requirements for Migrating vCenter Server Deployments to vCenter Server Appliance Deployments
- vCenter Server Appliance Requirements
- vCenter Server Appliance Hardware Requirements
- vCenter Server Appliance Storage Requirements
- Software Included in the vCenter Server Appliance
- vCenter Server Appliance Software Requirements
- vCenter Server Appliance Database Requirements
- vSphere Web Client Software Requirements
- Required Ports for vCenter Server and Platform Services Controller
- Pre-migration Checks
- Known Limitations
- Preparing for Migration
- Moving Update Manager to a New Host Machine When Migrating vCenter Server to vCenter Server Appliance
- Synchronizing Clocks on the vSphere Network
- Preparing vCenter Server Certificates for Migration
- Preparing vCenter Server Databases for Migration
- Prepare Managed ESXi Hosts for Migration
- Install the Client Integration Plug-In
- Required Information for Migrating vCenter Server and vCenter Single Sign-On from Windows to an Appliance
- Migration of vCenter Server with an Embedded vCenter Single Sign-On to an Appliance
- Migration of vCenter Server with an External vCenter Single Sign-On to an Appliance
- After Migrating vCenter Server
- Troubleshooting
- Index
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.
d (Optional) Select Performance and other historical data if you want to migrate this data.
By default only the core inventory and conguration data is migrated. Select the check box to
migrate all vCenter Server performance and historical data such as stats, events, alarms, and tasks.
Not migrating this data reduces the amount of overall downtime.
11 (Optional) Acknowledge the warning message, if any, by clicking Yes.
12 If the source vCenter Server is a member of an Active Directory domain, provide the credentials to join
the target vCenter Server Appliance to the domain.
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.
Medium (up to 400 hosts, 4,000
VMs)
Deploys an appliance with 8 CPUs, 24 GB of memory, and 300 GB of disk
space.
Large (up to 1,000 hosts, 10,000
VMs)
Deploys an appliance with 16 CPUs, 32 GB of memory, and 450 GB of disk
space.
Tiny (up to 10 hosts, 100 VMs, large
storage)
Deploys an appliance with 2 CPUs, 8 GB of memory, and 700 GB of disk
space.
Small (up to 100 hosts, 1,000 VMs,
large storage)
Deploys an appliance with 4 CPUs, 16 GB of memory, and 700 GB of disk
space.
Medium (up to 400 hosts, 4,000
VMs, large storage)
Deploys an appliance with 8 CPUs, 24 GB of memory, and 800 GB of disk
space.
Large (up to 1,000 hosts, 10,000
VMs)
Deploys an appliance with 16 CPUs, 32 GB of memory, and 900 GB of disk
space.
14 From the list of available datastores, select the location where all the virtual machine conguration les
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 seings.
The IP address or the FQDN of the appliance is used as a system name. It is recommended to use an
FQDN. However, if you want to use an IP address, use static IP address allocation for the appliance,
because IP addresses allocated by DHCP might change.
Chapter 6 Migration of vCenter Server with an Embedded vCenter Single Sign-On to an Appliance
VMware, Inc. 39