6.7

Each vCenter Server Appliance instance must have its own database. The bundled PostgreSQL
database that is included in the vCenter Server Appliance supports up to 2,000 hosts and 35,000 virtual
machines.
To ensure your database is prepared for migration:
n
Verify that passwords are current and not set to expire soon.
n
(Optional) Reduce the database size. For more information, see http://kb.vmware.com/kb/2110031.
n
Verify that you have backed up your database. See your database documentation.
n
Verify that vCenter Server can communicate with the local database. See 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 Deploys the target vCenter Server Appliance in an unconfigured state.
3 Copies exported data to the target vCenter Server Appliance.
4 Starts the PostgreSQL service to import the source database data.
5 Upgrades the database schema to be compatible with the target vCenter Server Appliance.
6 Starts the target vCenter Server Appliance services.
When you configure the target vCenter Server Appliance, you initialize and configure using the imported
database with the old schema. You have a choice of migration options:
1 Inventory tables
2 Inventory tables with events and tasks
3 All database 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 confirmed 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.
vCenter Server Upgrade
VMware, Inc. 145