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
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. See your database documentation.
n
Verify that vCenter Server can communicate with the local database.
During the migration of vCenter Server to vCenter Server Appliance, the installer:
1 Exports the vCenter Server database.
2 Copies exported data to the target vCenter Server Appliance.
3 Starts the PostgreSQL service to import the source database data.
4 Upgrades the database schema to be compatible with the target vCenter Server Appliance.
5 Starts the target vCenter Server Appliance services.
When you congure the target vCenter Server Appliance, you initialize and congure using the imported
database with the old schema. You have a choice of migration options:
1 Core data
2 Performance and other historical data
Prepare an Oracle Database for Migration
Ensure that you have the necessary credentials, and that you complete any necessary cleanup or other
preparation before migrating your Oracle database from Windows to an embedded PostgreSQL database in
the appliance.
Prerequisites
Verify that you have conrmed basic interoperability before preparing your Oracle database for migration.
Verify that you have backed up your database. For information about backing up the vCenter Server
database, see the Oracle documentation.
Procedure
1 Verify that passwords are current and not set to expire soon.
2 Ensure that you have login credentials, the database name, and the database server name that the
vCenter Server database is to use.
Look in the ODBC system for the connection name of the database source name for the vCenter Server
database.
3 Use the Oracle SERVICE_NAME instead of SID to verify that your Oracle database instance is available.
n
Log in to the database server to read from the alert log:
$ORACLE_BASE/diag/rdbms/$instance_name/$INSTANCE_NAME/trace/alert_$ INSTANCE_NAME.log.
n
Log in to the database server to read from the Oracle Listener status output.
n
If you have the SQL*Plus client installed, you can use tnsping for the vCenter Database instance. If
the tnsping command does not work the rst time, retry it after waiting a few minutes. If retrying
does not work, restart the vCenter Database instance on the Oracle server and then retry tnsping to
ensure it is available.
vSphere Migration
26 VMware, Inc.