Preparing vCenter Server Databases for Migration

The vCenter Server Appliance instance requires a database to store and organize server data. Ensure your source vCenter Server database is prepared for migration to the target vCenter Server Appliance.

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:

• Verify that passwords are current and not set to expire soon.
• (Optional) Reduce the database size. For more information, see http://kb.vmware.com/kb/2110031.
• 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:
  • Prepare an Oracle Database for Migration,
  • Prepare a Microsoft SQL Server Database for Migration
  • Prepare PostgreSQL Database Before Migrating vCenter Server to an Appliance
• Verify that you have backed up your database. See your database documentation.
• 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