VMware ESXI - 6.0.2 User Manual
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.
EN-002232-00
vSphere Migration
You can find the most up-to-date technical documentation on the VMware Web site at:
hp://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
System Requirements for Migrating vCenter Server Deployments to
1
vCenter Server Appliance Deployments 7
vCenter Server Appliance Requirements 9
2
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 Server and Platform Services Controller 12
Pre-migration Checks 17
3
Known Limitations 19
4
Preparing for Migration 21
5
Moving Update Manager to a New Host Machine When Migrating vCenter Server to
vCenter Server Appliance 21
Synchronizing Clocks on the vSphere Network 24
Preparing vCenter Server Certicates for Migration 25
Preparing vCenter Server Databases for Migration 25
Prepare Managed ESXi Hosts for Migration 28
Install the Client Integration Plug-In 30
Required Information for Migrating vCenter Server and vCenter Single Sign-On from Windows to
an Appliance 30
VMware, Inc.
Migration of vCenter Server with an Embedded vCenter Single Sign-On to an
6
Appliance 35
Download the vCenter Server Appliance Installer 36
Copy and Run VMware Migration Assistant on the Source vCenter Server Instance 36
Migrate vCenter Server with an Embedded vCenter Single Sign-On to an Appliance 37
Migration of vCenter Server with an External vCenter Single Sign-On to an
7
Appliance 41
Download the vCenter Server Appliance Installer 43
Copy and Run VMware Migration Assistant on the Source vCenter Server Instance 43
Migrate an External vCenter Single Sign-On instance to a Platform Services Controller appliance 44
Migrate vCenter Server to an Appliance 47
3
vSphere Migration
After Migrating vCenter Server 51
8
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
Troubleshooting 53
9
View Migration Assistant Logs and Status Files 53
Index 55
4 VMware, Inc.
About vSphere Migration
The vSphere Migration guide provides information about migrating VMware® vCenter Server to
vCenter Server Appliance.
To move to the current version of vSphere by performing a fresh installation that does not preserve existing
congurations, 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 hp://kb.vmware.com/kb/2146439.
Intended Audience
This information is intended for anyone who plans to migrate from earlier versions of vSphere. The
information is wrien for experienced Windows or Linux system administrators who are familiar with
virtual machine technology and data center operations.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For denitions
of terms as they are used in VMware technical documentation, go to
hp://www.vmware.com/support/pubs.
VMware, Inc.
5
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 specic 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
Synchronize the clocks on all machines running the source vCenter Server services. See “Synchronizing
n
Clocks on the vSphere Network,” on page 24.
Verify that the system network name of the machines running the target vCenter Server services are
n
valid, and are reachable from other machines in the network.
Verify that the host name of the virtual machine or physical server from which you are migrating
n
vCenter Server complies with RFC 1123 guidelines.
If your vCenter Server service is running using a user account other than the Local System account,
n
verify that the user account in which the vCenter Server service is running has the following
permissions:
Member of the Administrators group
n
Log on as a service
n
Act as part of the operating system (if the user is a domain user)
n
If your vCenter Server service is running using a service user account for access to the vCenter Server
n
database and you run Migration Assistant under a dierent account, the Migration Assistant account
must have the Replace a process level token permission.
Verify that the LOCAL SERVICE account has read permission on the folder in which vCenter Server is
n
installed and on the HKLM registry.
Verify that the connection between the virtual machine or physical server and the domain controller is
n
working.
Verify that the source vCenter Server instance or vCenter Single Sign-On instance on Windows have a
n
default gateway. If there is no default gateway, the migration will fail.
Verify that the source vCenter Server instance or vCenter Single Sign-On instance on Windows does not
n
use a DHCP IP address as its system network name.
I Migration from a source Windows machine using a DHCP IP Address as its system
network name to an appliance is not supported.
VMware, Inc.
7
vSphere Migration
Target System
Your target system must meet specic software and hardware requirements for
n
vCenter Server Appliance. See Chapter 2, “vCenter Server Appliance Requirements,” on page 9.
When you use Fully Qualied Domain Names, make sure that the machine you use for deploying the
n
vCenter Server Appliance and the target ESXi host or vCenter Server instance are on the same DNS
server.
Synchronize the clocks of all target virtual machines on the vSphere network before beginning
n
migration. Unsynchronized clocks might result in authentication problems and can cause the migration
to fail or prevent the vCenter Server services from starting. See “Synchronizing Clocks on the vSphere
Network,” on page 24.
8 VMware, Inc.
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
specic software and hardware requirements.
When you use Fully Qualied 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. Unsynchronized clocks might result in authentication problems and can
cause the installation to fail or prevent the vCenter Server Appliance services from starting. See
“Synchronizing Clocks on the vSphere Network,” on page 24.
This chapter includes the following topics:
“vCenter Server Appliance Hardware Requirements,” on page 9
n
“vCenter Server Appliance Storage Requirements,” on page 10
n
“Software Included in the vCenter Server Appliance,” on page 11
n
“vCenter Server Appliance Software Requirements,” on page 11
n
“vCenter Server Appliance Database Requirements,” on page 11
n
“vSphere Web Client Software Requirements,” on page 11
n
“Required Ports for vCenter Server and Platform Services Controller,” on page 12
n
vCenter Server Appliance Hardware Requirements
When you deploy the vCenter Server Appliance, you can select to deploy an appliance that is suitable for
the size of your vSphere environment. The option that you select determine the number of CPUs and the
amount of memory that the appliance will have.
The hardware requirements such as number of CPUs and memory depend on the size of your vSphere
inventory.
VMware, Inc.
9
vSphere Migration
Table 2‑1. Hardware Requirements for VMware vCenter Server Appliance
Tiny
Environment
(up to 10
Hosts, 100
Platform Services
Resources
Number of CPUs 2 2 4 8 16
Memory 2 GB RAM 8 GB RAM 16 GB RAM 24 GB RAM 32 GB RAM
Controller
Virtual
Machines)
Small
Environment
(up to 100
Hosts, 1,000
Virtual
Machines)
I For vCenter Server Appliance with an embedded Platform Services Controller, you must add
the hardware requirements for Platform Services Controller to the hardware requirements for
vCenter Server Appliance depending on the size of your environment.
vCenter Server Appliance Storage Requirements
When you deploy the vCenter Server Appliance, the host on which you deploy the appliance must meet
minimum storage requirements. The required storage depends not only on the size of the vSphere
environment, but also on the disk provisioning mode.
The storage requirements depend on the deployment model that you select to deploy.
Medium
Environment
(up to 400
Hosts, 4,000
Virtual
Machines)
Large
Environment
(up to 1,000
Hosts, 10,000
Virtual
Machines)
Table 2‑2. vCenter Server Minimum Storage Requirements Depending On the Deployment Model
External
Platform
Tiny
environment (up
to 10 hosts, 100
virtual
machines)
Small
environment (up
to 100 hosts,
1,000 virtual
machines)
Medium
environment (up
to 400 hosts,
4,000 virtual
machines)
Large
environment (up
to 1,000 hosts,
10,000 virtual
machines)
vCenter Server Appliance with an
Embedded
Platform Services Controller
Default
Storage Size Large Storage Size
120 GB 700 GB 120 GB 700 GB 30 GB
150 GB 700 GB 150 GB 700 GB 30 GB
300 GB 800 GB 300 GB 800 GB 30 GB
450 GB 900 GB 450 GB 900 GB 30 GB
vCenter Server Appliance with an
External
Platform Services Controller
Default
Storage Size Large Storage Size
Services
Controller
Appliance
Default Storage
Size
10 VMware, Inc.
Chapter 2 vCenter Server Appliance Requirements
Software Included in the vCenter Server Appliance
The vCenter Server Appliance is a precongured Linux-based virtual machine optimized for running
vCenter Server and associated services.
The vCenter Server Appliance package contains the following software:
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.
n
vCenter Server Appliance Software Requirements
The VMware vCenter Server Appliance can be migrated only on hosts that are running ESXi version 5.0 or
later.
You can migrate the vCenter Server Appliance only by using the Client Integration Plug-In, which is an
HTML installer for Windows that you can use to connect directly to an ESXi 5.0.x, ESXi 5.1.x, ESXi 5.5.x, or
ESXi 6.0 host and migrate the vCenter Server Appliance on the host.
I You cannot migrate the vCenter Server Appliance by using the vSphere Client or the
vSphere Web Client. During the migration of the vCenter Server Appliance you must provide various
inputs, such as operating system and vCenter Single Sign-On passwords.
vCenter Server Appliance Database Requirements
The vCenter Server Appliance requires a database to store and organize server data.
Each vCenter Server Appliance instance must have its own database. When you migrate vCenter Server to
vCenter Server Appliance the database is migrated to an internal PostgreSQL database, which supports up
to 1,000 hosts and 10,000 virtual machines.
vSphere Web Client Software Requirements
Make sure that your browser supports the vSphere Web Client.
The vSphere Web Client 6.0 requires Adobe Flash Player 16 or later. The latest Adobe Flash Player version
for Linux systems is 11.2. Therefore, the vSphere Web Client cannot run on Linux platforms.
VMware has tested and supports the following guest operating systems and browser versions for the
vSphere Web Client. For best performance, use Google Chrome.
Table 2‑3. Supported Guest Operating Systems and Minimum Browser Versions for the
vSphere Web Client
Operating system Browser
Windows Microsoft Internet Explorer 10.0.19 and later.
Mozilla Firefox 34 and later.
Google Chrome 39 and later.
Mac OS Mozilla Firefox 34 and later.
Google Chrome 39 and later.
VMware, Inc. 11
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.
Ports Required for Communication Between Components
If a port is in use or is blacklisted, the vCenter Server installer displays an error message. You must use
another port number to proceed with the installation. There are internal ports that are used only for interprocess communication.
VMware uses designated ports for communication. Additionally, the managed hosts monitor designated
ports for data from vCenter Server. If a rewall exists between any of these elements, the installer opens the
ports during the installation or upgrade process. For custom rewalls, you must manually open the required
ports. If you have a rewall between two managed hosts and you want to perform source or target activities,
such as migration or cloning, you must congure a means for the managed hosts to receive data.
N In Microsoft Windows Server 2008 and later, rewall is enabled by default.
If you congured a custom port when you installed the source vCenter Server instance, revert to default port
values before you proceed with the migration.
Table 2‑4. Ports Required for Communication Between Components
Port Protocol Description Required for
22 TCP/UDP System port for SSHD.
I This port must be open
during the migration to an appliance.
The migration process establishes an
SSH connection to transfer the data
from the existing to the new
appliance.
80 TCP vCenter Server requires port 80 for
direct HTTP connections. Port 80
redirects requests to HTTPS port 443.
This redirection is useful if you
accidentally use hp://server instead
of hps://server.
WS-Management (also requires port
443 to be open).
If you use a Microsoft SQL database
that is stored on the same virtual
machine or physical server as the
vCenter Server, port 80 is used by the
SQL Reporting Service. When you
install or upgrade vCenter Server, the
installer prompts you to change the
HTTP port for vCenter Server.
Change the vCenter Server HTTP
port to a custom value to ensure a
successful installation or upgrade.
I You can change this port
number during the vCenter Server
and Platform Services Controller
installations on Windows.
Appliance
deployments of
vCenter Server
n
Platform Services
n
Controller
Windows
installations and
appliance
deployments of
vCenter Server
n
Platform Services
n
Controller
Used for Node-toNode
Communication
No
No
12 VMware, Inc.
Chapter 2 vCenter Server Appliance Requirements
Table 2‑4. Ports Required for Communication Between Components (Continued)
Port Protocol Description Required for
88 TCP Active Directory server. Windows
installations and
appliance
deployments of
Platform Services
Controller
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. If another
service is running on this port, it
might be preferable to remove it or
change its port to a dierent port. You
can run the LDAP service on any port
from 1025 through 65535.
If this instance is serving as the
Microsoft Windows Active Directory,
change the port number from 389 to
an available port from 1025 through
65535.
443 TCP The default port that the
vCenter Server system uses to listen
for connections from the
vSphere Web Client. To enable the
vCenter Server system to receive data
from the vSphere Web Client, open
port 443 in the rewall.
The vCenter Server system also uses
port 443 to monitor data transfer from
SDK clients.
This port is also used for the
following services:
WS-Management (also requires
n
port 80 to be open)
Third-party network
n
management client connections to
vCenter Server
Third-party network
n
management clients access to
hosts
I You can change this port
number during the vCenter Server
and Platform Services Controller
installations on Windows.
514 UDP vSphere Syslog Collector port for
vCenter Server on Windows and
vSphere Syslog Service port for
vCenter Server Appliance
I You can change this port
number during the vCenter Server
and Platform Services Controller
installations on Windows.
Windows
installations and
appliance
deployments of
Platform Services
Controller
Windows
installations and
appliance
deployments of
vCenter Server
n
Platform Services
n
Controller
Windows
installations and
appliance
deployments of
vCenter Server
n
Platform Services
n
Controller
Used for Node-toNode
Communication
No
vCenter Server to
n
Platform Services
Controller
Platform Services
n
Controller to
Platform Services
Controller
vCenter Server to
n
vCenter Server
vCenter Server to
n
Platform Services
Controller
Platform Services
n
Controller to
vCenter Server
No
VMware, Inc. 13
vSphere Migration
Table 2‑4. Ports Required for Communication Between Components (Continued)
Port Protocol Description Required for
636 TCP vCenter Single Sign-On LDAPS Windows
902 TCP/UDP The default port that the
1514 TCP/UDP vSphere Syslog Collector TLS port for
2012 TCP Control interface RPC for vCenter
2014 TCP RPC port for all VMCA (VMware
2020 TCP/UDP Authentication framework
vCenter Server system uses to send
data to managed hosts. Managed
hosts also send a regular heartbeat
over UDP port 902 to the
vCenter Server system. This port
must not be blocked by rewalls
between the server and the hosts or
between hosts.
Port 902 must not be blocked between
the vSphere Client and the hosts. The
vSphere Client uses this port to
display virtual machine consoles
I You can change this port
number during the vCenter Server
installations on Windows.
vCenter Server on Windows and
vSphere Syslog Service TLS port for
vCenter Server Appliance
I You can change this port
number during the vCenter Server
and Platform Services Controller
installations on Windows.
Single Sign-On
Certicate Authority) APIs
I You can change this port
number during the
Platform Services Controller
installations on Windows.
management
I You can change this port
number during the vCenter Server
and Platform Services Controller
installations on Windows.
installations and
appliance
deployments of
Platform Services
Controller
Windows
installations and
appliance
deployments of
vCenter Server
Windows
installations and
appliance
deployments of
vCenter Server
n
Platform Services
n
Controller
Windows
installations and
appliance
deployments of
Platform Services
Controller
Windows
installations and
appliance
deployments of
Platform Services
Controller
Windows
installations and
appliance
deployments of
vCenter Server
n
Platform Services
n
Controller
Used for Node-toNode
Communication
vCenter Server to
Platform Services
Controller
No
No
vCenter Server to
n
Platform Services
Controller
Platform Services
n
Controller to
vCenter Server
Platform Services
n
Controller to
Platform Services
Controller
vCenter Server to
n
Platform Services
Controller
Platform Services
n
Controller to
vCenter Server
vCenter Server to
n
Platform Services
Controller
Platform Services
n
Controller to
vCenter Server
14 VMware, Inc.
Chapter 2 vCenter Server Appliance Requirements
Table 2‑4. Ports Required for Communication Between Components (Continued)
Used for Node-toNode
Port Protocol Description Required for
5480 TCP vCenter Server Appliance Web user
interface (HTTPS)
6500 TCP/UDP ESXi Dump Collector port
I You can change this port
number during the vCenter Server
installations on Windows.
6501 TCP Auto Deploy service
I You can change this port
number during the vCenter Server
installations on Windows.
6502 TCP Auto Deploy management
I You can change this port
number during the vCenter Server
installations on Windows.
7444 TCP Secure Token Service Windows
9443 TCP vSphere Web Client HTTPS Windows
11711 TCP vCenter Single Sign-On LDAP - For backward
11712 TCP vCenter Single Sign-On LDAPS - For backward
Appliance
deployments of
vCenter Server
n
Platform Services
n
Controller
Windows
installations and
appliance
deployments of
vCenter Server
Windows
installations and
appliance
deployments of
vCenter Server
Windows
installations and
appliance
deployments of
vCenter Server
installations and
appliance
deployments of
Platform Services
Controller
installations and
appliance
deployments of
vCenter Server
Communication
No
No
No
No
vCenter Server to
n
Platform Services
Controller
Platform Services
n
Controller to
vCenter Server
No
compatibility with
vSphere 5.5 only.
vCenter Single SignOn 5.5 to
Platform Services
Controller 6.0
compatibility with
vSphere 5.5 only.
vCenter Single SignOn 5.5 to
Platform Services
Controller 6.0
Custom Ports
If you congured custom ports for Auto Deploy or vSphere ESXi Dump Collector, these custom ports are
migrated to the conguration of the target vCenter Server Appliance. For example, if you congured Auto
Deploy to use port 6545, the conguration is migrated to the target vCenter Server Appliance. Other custom
ports are not supported in the vCenter Server Appliance.
VMware, Inc. 15
vSphere Migration
To congure the vCenter Server system to use a dierent port to receive vSphere Web Client data, see the
vCenter Server and Host Management documentation.
For more information about rewall conguration, 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 veries 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.
If your vCenter Server service is running in a service user account for access to the vCenter Server database
and you run Migration Assistant under a dierent account, the Migration Assistant account must have the
Replace a process level token permission.
The pre-migration checker performs checks for the following aspects of the source environment:
Network connections
n
Internal and external port availability
n
Administrator privileges on the Windows machine
n
Any credentials that you enter
n
Supported product and version
n
Administrator privilege for launching Migration Assistant
n
Migration Assistant port availability
n
Export directory space and permission requirements
n
System name validity
n
Inventory size compatibility
n
External vCenter Single Sign-On version
n
vCenter Single Sign-On and vCenter Server certicate compatibility
n
NTP server validity
n
Target Environment Checks
The pre-migration checker performs checks for the following aspects of the target environment:
Network connections
n
Target vCenter Server IP address
n
VMware, Inc.
17
Loading...