As you may or may not know, the new vCenter 4.1 requires that the host it runs on is 64 bit. As 4.0 and previous versions weren’t supported on 64 bit at all, this probably means that when you upgrade you will need to move your existing database to a new host.
There are several ways of doing the migration, but one way is to backup your existing database, and restore it on a new host and point the new vCenter 4.1 installation to the existing database and have it upgrade it for you during install.
I’m sure that you would like to automate that process, just to limit the possibility of manual screw ups, right? Thankfully, VMware had the same idea.
In chapter 5 of the vSphere Upgrade Guide, VMware outlines the different methods you can use when migrating your vCenter database, and on page 39 a data migration tool makes it’s appearance.
This two step process takes a backup of your existing vCenter SQL Server Express database and dumps it to a predefined local folder. You then copy the entire migration tool folder to the new host and run the second part of the tool to install vCenter 4.1 and import the old database.
I used this tool to migrate our setup, from Windows Server 2003 32bit to Windows Server 2008 R2 64bit without problems.
**The only thing you need to be aware of is that VMware Update Manager is still a 32bit application and requires that you manually create a 32bit DSN to the database. This is mentioned in the VUM Installation and Administration Guide, but it is not mentioned in the vSphere Upgrade Guide. **
All in all, this tool is a great assistant for all of you that need to migrate to a new host for 64bit support in vCenter Server 4.1. While it could be more polished, brand a GUI and let you use network storage for the backups, it does the job at hand very well. After all, who needs a polished GUI based application for a one off job like this?
Related VMware Knowledgebase Articles #
- vSphere 4.1 upgrade pre-installation requirements and considerations
- Migrating an existing vCenter Server database to 4.1 using the data migration tool
- vCenter Server 4.1 Data Migration Tool fails with the error: HResult 0x2, Level 16, State 1
- Using the Data Migration Tool to upgrade from vCenter Server 4.0 to vCenter Server 4.1 fails
- vCenter Server 4.1 Performance and Best Practices —
- Monitoring the ESXi Upgrade Process —
- Installing and Configuring WANem Virtual Appliance —
- Developer meets PowerCLI - awesomeness ensues —
- vCenter 4.1 Database Recovery Model Defaults —