Portal Home > Knowledgebase > VMware Knowledge Base > Migrating to vCenter Server 5.0 using the Data Migration Tool

Migrating to vCenter Server 5.0 using the Data Migration Tool

Purpose

You can use the Data Migration Tool to back up VirtualCenter or vCenter Server configuration data such as port settings, SSL certificates, and licensing information. The Data Migration Tool can restore these settings when you upgrade to vCenter Server 5.0 on a new 64-bit machine.
 
vCenter Server 5.0 is supported only on 64-bit operating systems. There is no in-place upgrade path for a vCenter Server 5.0 installation on a 32-bit operating system. If your existing vCenter Server is installed on a 32-bit operating system, you need to migrate to a 64-bit operating system where vCenter Server 5.0 can be installed.
 
This article provides an overview of how to use the database migration procedure using the vCenter Server 5.x Data Migration Tool. For details on information preserved by the Data Migration Tool, see vSphere 5.0 upgrade pre-installation requirements and considerations (2004265).
 
Notes:
  • The Data Migration Tool can only be used to migrate the SQL Express databases that comes bundled with vCenter Server. Any other databases, such as IBM DB/2, Oracle, and Microsoft SQL 2008 Standard Edition are not supported. For more information, see vSphere 5.0 upgrade pre-installation requirements and considerations (2004265).
  • This data migration tool is not supported for vCenter Server 5.1. You cannot directly migrate an existing vCenter Server to a new machine during an upgrade to version 5.1. You can migrate an existing vCenter Server to a new machine during an upgrade to version 5.0, then perform an in-place upgrade from version 5.0.

Resolution

Notes:
  • This article assumes that you have read the vSphere 5.0 Upgrade Guide and have understood the risks associated with migrating your database. This guide contains definitive information. If there is a discrepancy between the guide and this article, assume that the guide is correct.
  • Ensure that you have made a full backup of the existing vCenter Server database. For more information on backing up your database, see the Microsoft article How to: Back Up a Database (SQL Server Management Studio) 
If your database is a SQL Server Express database that is local to the VirtualCenter or vCenter Server machine, the Data Migration Tool backs up the database and restores it to the destination machine.
 
If VMware vCenter Orchestrator is installed on the same machine as VirtualCenter or vCenter Server, the Data Migration Tool backs up the vCenter Orchestrator configuration and restores it to the destination machine. The Data Migration Tool does not back up and restore the vCenter Orchestrator database. See the VMware vCenter Orchestrator documentationfor information about upgrading vCenter Orchestrator using the Data Migration Tool.
 
If VMware vCenter Update Manager is installed on the same machine as VirtualCenter or vCenter Server, the Data Migration Tool backs up the vCenter Update Manager configuration and restores it to the destination machine. If vCenter Update Manager uses a SQL Server Express database that is local to the source machine, the Data Migration Tool backs up the database and restores it to the destination machine. The Data Migration Tool does not back up and restore patch binaries. See the VMware vCenter Update Manager documentation for information about upgrading vCenter Update Manager with the Data Migration Tool.  

Prerequisites

To use the Data Migration Tool, ensure that you:
  • Verify that a supported version of VirtualCenter or vCenter Server is installed on the source machine. These versions are supported:
    • VirtualCenter 2.5 Update 6 or later
    • vCenter Server 4.0.x and its update releases

vCenter Server 4.1.x is not supported for the data migration tool 

  • Stop the VMware VirtualCenter Server service before backing up the configuration. For more information, seeStopping, starting, or restarting vCenter services (1003895). 
  • If the \datamigration\data\ folder already exists from a previous backup attempt, backup cannot proceed. Remove or rename this folder before backing up the vCenter Server configuration.
  • If you are using a bundled database for VirtualCenter 2.5 Update 6 or vCenter Server 4.x, make sure that named pipes are not disabled and that the pipe name is correct. Change the default pipe name to\\.\pipe\sql\query.
  • If you are using a bundled database, make sure that you do not change the DSN name. It should be VMware vCenter. If the DSN name is changed, the backup operation fails. 
  • If are you using vCenter Orchestrator 4.0 or an update release, verify it is installed and configured. Stop the VMware vCenter Orchestrator Configuration, VMware vCenter Orchestrator Server, and VMware vCenter Server services. For more information, see Stopping, starting, or restarting vCenter services (1003895). 
  • If you migrating a Update Manager, the database must be the SQL Server Express database installed on the same machine as Update Manager. Stop the Update Manager service when performing a migration. 
  • If Update Manager server and vCenter Server are installed on the same machine, they must use dedicated databases (that is, the servers must not share one database instance). 
Note: The Data Migration Tool does not change the hostname or IP address of the target vCenter Server to match that of your existing vCenter Server. Services such as VMware HA and Update Manager expect the IP address and hostname to be the same. VMware recommends that you retain the existing hostname and IP address on the target vCenter Server when possible. If it is not possible to retain these settings, see vCenter Server IP address change causes ESX hosts to disconnect (1001493) and How to reconfigure Update Manager after a change of the vCenter Server IP Address (1014639).     

Preparing the database for migration

To prepare the database for migration: 
  1. Open the folder datamigration on the root of the vCenter Server 5.0 installation media that you have downloaded from the VMware website.
  2. Copy the datamigration.zip file from that folder and extract it to the root of your C: drive.
  3. Click Start > Run, type services.msc, and click OK.
  4. Stop these services:
    • VMware Update Manager Service
    • VMware VirtualCenter Management Webservices
    • VMware VirtualCenter Server Service

      Note: For more information, see Stopping, starting, or restarting vCenter services (1003895).
  5. Click Start > Run, type cmd, and click OK.
  6. Type cd \datamigration to change to the datamigration folder.
  7. Run this command to copy the VirtualCenter or vCenter Server configuration:

    backup.bat
     
Migrating the database to vCenter Server 5.0
 
Note: Services need not be stopped on the target server, unless vCenter Server 5.0 has already been installed. If vCenter Server 5.0 is already installed, uninstall the existing installation and let the Data Migration Tool install vCenter Server 5.0 for you. In addition, when performing a migration to the target server, a DSN is not automatically created. This must be manually created on the target server after the database is migrated. For more information, see the vSphere 5.x Upgrade Guide. 
 
To migrate the database to vCenter Server 5.0:
  1. Copy the contents of the c:\datamigration folder from the existing vCenter Server to your target server's C:drive in the same location.
  2. Mount the vCenter Server 5.0 installation media on your local CD-ROM drive.

    Note: Close the autorun menu, if it opens. It is not necessary to complete the migration.
  3. Click Start > Run, type cmd, and click OK.
  4. Type cd \datamigration to change to the datamigration folder.
  5. Run the following command to start the installation migration:

    install.bat

    Note: This script asks you for the vCenter Server 5.0 installation media path.
     
  6. Follow the installation wizard.

    Based on VMware KB 2005328

Also Read

Language: