Database Relocation & vSphere Upgrade (4.0 to 4.1)

[mbaberjm]

Hi.

I need some input regarding the sequence that I should take for upgrading from vSphere 4.0 to 4.1, and relocating my sql database.

Background Info.

1. I am running 7 hosts (ESXi 4.0), and 58 VMs with more to be added.

2. My vCenter server (4.0) is running on a virtual Win2003 server 32-bit, with sql2005 express.

3. My Update Manager is on another VM running Win2008 server 64-bit.

4. I have a central VM running SQL 2005 std.

5. I have a pending approval for purchase of MS SQL 2008.

I would like to relocate my vCenter database to the central SQL server as I am over the 5 host & 50 VM limit.

Then upgrade both my hosts and vCenter to 4.1, then upgrade my SQL environment from 2005 to 2008 at a later date.

Will vSphere 4.1  run against a central 32-bit SQL 2005 environment if I relocate the database before upgrading to vSphere 4.1, and I upgrade my SQL environment later?

[jamesbowling]

Check out these KB articles:

http://kb.vmware.com/kb/1022137

http://kb.vmware.com/kb/1022104

Those will probably point you in the right direction.

[nkrishnan]

Hi,

Your vCenter Update Manager can continue working with SQL 2005 32 bit, but vCenter server cannot work with 32bit DB. vCenter server 4.1 is a 64bit application and it need 64bit OS and DSN.

-Nithin

[Henry_Dorset_Ca]

Hi,

I would like to relocate my vCenter database to the central SQL server as I am over the 5 host & 50 VM limit.

Then upgrade both my hosts and vCenter to 4.1, then upgrade my SQL environment from 2005 to 2008 at a later date.

Will  vSphere 4.1  run against a central 32-bit SQL 2005 environment if I  relocate the database before upgrading to vSphere 4.1, and I upgrade my  SQL environment later?

The answer is yes. vCenter 4.1 will run against a 32bit version of SQL Server 2005. Cf. http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf  - Just remember that you will need to use MS SQL 2005 SP1 or newer.

BTW, you can use the VMware Datamigration tool to migrate all the internal settings of your recent vCenter installation even if you're migrating from a bundeled database to an unbundeled database. As you already stated, backup and restore your SQL Express database to the new SQL 2005 platform. Just recently I stumbled over the problem that a backed-up SQL 2005 Express vCenter 4.0 database couldn't be restored on SQL 2005 SP1 Standard. After detaching and copying the mdf and ldf files to the new server just attach the old database and it will run fine. The DSN you have to create to use this database should have the same name (VMware VirtualCenter) and should point to the same DB-Name (VIM_VCDB). Remember the prerequisites for the DSN owner account etc. pp - just check the Upgrade Guide http://www.vmware.com/pdf/vsphere4/r41/vsp_41_upgrade_guide.pdf

Then run the Datamigration Tool on your old vCenter Server and just discard the backed-up SQL Express database and the already converted (DMT does this automatically) database in the ...\datamigration\data folder. Copy the altered ...\datamigration\ file structure to the new location, insert the vCenter installation media to an appropriate physical or virtual drive, start the install batch in the datamigration folder, convert your database and here you go. EDIT: Just check that all the database jobs previously owned and triggered by SQL Express are configured to run with the SQL Agent and run witout errors. Check http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100438.... You also might want to check the necessary stored procedures for your vCenter database. There are 28 stored procedures configured by default for the vCenter database. In case of troubles check http://communities.vmware.com/thread/276714. You will get some useful hints in this thread.

SQL2008 offers various ways (including wizards) to migrate or upgrade previous versions of SQL Server.

HtH

Cheers

HDC

Orthographic corrections by HDC