Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 207710

Migration from vCenter 4.0 to new 5.0 server with bundled Express DB upgraded to Standard Edition

$
0
0

Hi,

 

I'm testing the VMware steps fro migrating vCenter 4.0 to 5.0 on another new server.  Our vCenter 4 was originally installed with the Bundled SQL Express DB. Over the years we've outgrown this Express DB, and have upgraded to Standard Edition on the same local machine.

 

As part of the vmware steps for the vCenter Unbundled DB migration, I've already successfully backed-up & restored SQL Standard Edition DB from the 4.0  vm to the new 5.0 vm

 

However, when I now run the Data Migration Tool on the vCenter 4.0 vm, to capture the remaining data: ADAM, LDAP, ports,etc..  , the Data Migration Tool still detects the SQL DB type as Bundled, even though we've upgraded it to Standard Edition in the past, and its 16GB in size.  I suspect this detection is tied to the Instance name SQLEXP_VIM which is a Vmware normal naming convention for the Bundled DB

 

Is there anyway to skip this DB backup when the Data Migration Tool runs?

Or would the Tool successfully backup and restore this 16GB Standard Edition DB?

 

I'm reluctant to proceed with the Data Migration Tool backup.bat in case it may corrupt the sql db, or attempt make some sort of of change to it.

 

PS. I'm following the steps from page 42 onwards of this document:

http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-upgrade-guide.pdf


Viewing all articles
Browse latest Browse all 207710

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>