I’m into my second day on this project. It appears that the backup and restore procedures run to completion but on the target machine the database is empty. This is pretty easy to check; I just went in with SQL Management Studio, looked in VIM_VCDB -> Tables -> dbo.VPX_DATASTORE and did “Open Table.” On the source machine I saw all the datastores in there (as expected). On the target machine, however, the table was empty.
I found KB 1024380 describing a failure of the migration tool with a symptom, “Data Migration Tool logs (restore.log) does not indicate any errors, but the database is blank.” The KB says:
This known issue occurs when the Data Migration Tool is run against a vCenter Server with MS SQL Express that has been updated (for example, if vCenter Server 4.0 is updated to Update 2 or if vCenter Server 2.5 is updated to vCenter Server 4.0.)
Well, that’s me – we went from 3.5 to 4.0. I made the registry change and went through the procedure again (vCenter and Update Manager must be uninstalled from the target machine before attempting to restore again).
It worked! After changing the registry key everything appears to have been copied over. I feel dumb for having wasted so much time on this, but oh well. Moral of the story: Google Early and Google Often. vCenter appears to be working fine (with a nice performance boost since the VM it’s now on has 4GB ram). I ended up moving it into the cluster – our ESX hardware is just so much better than the machine it had been running on. I’m still not totally sold on the idea but it does make things simpler. If it ends up causing problems I can always move it back.
Next step: migrating from ESX 4.0 to ESXi 4.1.