Since they were already running SQL 2005 we didn’t see the need to move the database or upgrade SQL since 2005 is supported by vCenter 4.1.ĭuring the install of vCenter 4.1 the database upgrade processes started as normal but then about 5 minutes into it we received this error “Exception Thrown while executing SQL script” and the install was halted. In this case the client was running SQL 2005 as their database server for vCenter 2.5. On my most recent upgrade/migration I ran into an SQL issue that I hadn’t seen before. The tool will also backup and restore SQL Express databases but most of our clients are running full SQL. The data migration tool is handy for backing up the SSL certificates and registry settings from the vCenter 2.5 server and then restoring those to the new vCenter 4.1 server. Most of our clients that are on vCenter 2.5 are running it on 32-bit versions of Windows with most of those being Windows 2003.įor these migrations we have mostly been building new Windows 2008 R2 virtual machines and using the new vCenter Data Migration tool – Migrating an existing vCenter Server database to 4.1 using the Data Migration Tool Upgrades to 4.1 have been more difficult than doing upgrades to 4.0 because vCenter 4.1 requires an 圆4 version of Windows. I have recently been doing vCenter 2.5/4.0 to vCenter 4.1 upgrades and migrations for our clients.