The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Moving the VMware vCenter Server 4.x/5.x SQL database (7960893)
To move SQL Server databases used by vCenter Server to a new location:
- Stop the VMware VirtualCenter Server, VMware VirtualCenter Management Webservices and VMware Update Manager services. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Note: For vCenter Server 5.0.x, stop the vCenter Inventory Service and VMware vSphere Profile-Driven Storage service.
- Migrate the VCDB and UMDB from the existing SQL instance to the new SQL instance running on the remote server. For information on migrating databases, see Back Up and Move a Local vCenter Server Database.
- If migrating a vCenter Server 4.x local database, you may also need to migrate the ADAM database. For more information, see Manually backing up and restoring the vCenter Server 4.x and 5.0 ADAM instance data (1029864).
- Note the credentials and server that vCenter Server uses to connect to the database. Update the DSN as necessary to the migrated database. For more information, see vCenter Server installation fails with ODBC and DNS errors (1003928).
- Recreate SQL Agent rollup jobs. Detaching, attaching, importing, and restoring a database to a newer version of SQL Server does not automatically recreate these jobs. For more information, see Updating rollup jobs after the error: Performance data is currently not available for this entity (1004382).
Note: SQL Server Agent is not available in Microsoft SQL Server 2005 and 2008 Express.
For a complete list of the jobs that should be present, see:
- Verifying vCenter Server 2.5 jobs and stored procedures (1033588)
- Verifying vCenter Server 4.0 jobs and stored procedures (1033587)
- Verifying vCenter Server 4.1 jobs and stored procedures (1029824)
- Verifying jobs and stored procedures installed in vCenter Server 5.0 (2006097)
- Verifying jobs and stored procedures installed in vCenter Server 5.1 and 5.5 (2033096)
- Update the
vcdb.propertiesfile with the new SQL server. If this is not updated, the performance overview charts and the Storage Monitoring Service (SMS) may be affected after migrating the vCenter Server database. For more information, see VMware vCenter Storage Monitoring Service fails with the error: Service initialization failed (2016472). The
vcdb.propertiesfile is located at:
- Windows 2008 –
- Other Windows versions –
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\
- Windows 2008 –
- Start the VMware VirtualCenter Server and VMware Update Manager services. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Note: In vCenter Server 5.1 and above, ensure that the Single Sign-On Service is started before starting the VMware VirtualCenter Server service.
- Database server compatibility, see the Compatibility Matrix.
- Moving VirtualCenter to a new server, see Migrating VirtualCenter to a different Server (5850444).
- Changing the vCenter Server database user ID and password, see Changing the vCenter Server database user ID and password (1006482).
- When moving or relocating the Single Sign-On Server to a new database, see Update vCenter Single Sign On settings after you change the host name or port of the database server (2033516).
- Resolving the Update Manager issues after a database migration, see Enabling Update Manager fails with the error: database unavailable or has network problems (1015223).
- For more information on verifying jobs and stored procedures, see Verifying jobs and stored procedures installed in vCenter Server 5.1 and 5.5 (2033096).
- For more information on errors with ports in use after migrating the database, see Port already in use when installing VMware vCenter Server 4.x / 5.x (4824652) and TCP and UDP Ports required to access vCenter Server, ESXi/ESX hosts, and other network components (1012382).
When moving a SQL database from one server to another, you must follow all recommendations and steps provided by the third-party vendor. For more information on:
- Attaching and detaching a database for Microsoft SQL Server, see Microsoft Knowledge Base article 224071.
- Using the Copy Database Wizard in SQL Server 2000, see Microsoft Knowledge Base article 274463.
- Syntax or best practices, engage the third-party vendor's documentation or support.
- Moving SQL Server 2008 R2, see the MSDN article on Moving Database Files.
Additional InformationFor translated versions of this article, see:
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.