[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1129
  • Last Modified:

vCenter 4 server migration

I have a vCenter 4 server on a machine
Server Hostname: "server1"
IP: "10.10.10.10"
OS: windows 2003 SP1 STD
DB: SQL 2005 Express

I need to move the vCenter 4 server to another machine
Server Hostname: "server2"
IP: "10.10.10.20"
OS: windows 2003 SP1 STD
DB: SQL 2005 Express

What is the best way?
I have been looking all over the net for a migration step-by-step, but none was help for my scenario.
Appreciate some help from you guys here.
Thanks
Dan
0
silterra
Asked:
silterra
  • 5
  • 2
1 Solution
 
bbnp2006Commented:
First you need to do is to backup your database on your existing vCenter 4 server. It's safe to stop all the vmware services first, then do a database backup.
Restore this database at the server2--> install vCenter server 4 on server2 --> using the restored database during your vCenter server installation wizard. You should be good to go.
Leave your server1 powered off for few days until you can verify everything is working before you decommission it.
Hope this helps.
0
 
silterraAuthor Commented:
bbnp2006: I did just that ....it didn't work. Does the change of hostname and IP cause any complications to the transfer?
 
0
 
bbnp2006Commented:
When you say it didn't work, can you be a bit more specific? any error message?
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
bbnp2006Commented:
On your Virtual Center, did you grant user account grant  DBO access to the newly attached database?
0
 
bbnp2006Commented:
Here's a detailed step I would do in your scenario:
    * Take backup of Server A sql database
    * Stop all VMware services on Server A
    * Detach Virtual Center database on Server A
    * Stop all VMware services on Server B
    * Delete the Virtual Center database on Server B (database was empty and was created for the installation of Virtual Center on the new server.
    * Copy the database files from Server A to Server B
    * Attach the database on Server B
    * On your Virtual Center user account(s) grant them DBO access to the newly attached database
    * Start the VMware services on Server B
    * Launch the VI Client form Server B
    * You will notice that after a few minutes the ESX hosts will show disconnected because they still think they are being managed by the old Virtual Center Server
    * Right-click and remove the ESX hosts from the cluster
    * Add the ESX hosts back to the cluster
    * Adding the ESX hosts back to the cluster does not put the VM's into any Resource Pools (Hosts and Clusters View) or Folders (VM and Templates View). Move VM's back to the correct Resource Pools and Folders
    * On each ESX host ensure that the licensing information looks correct
    * Test vMotion
    * Add templates back to inventory
    * Move SysPrep files from old Virtual Center Server to new Virtual Center Server
    * Test deploying VM from template.

And yes, you can do this during normal work hour since all VMs will not get affected, but your DRS and vMotion will not work until your new vCenter server comes online again.

Good luck.
0
 
silterraAuthor Commented:
It worked perfectly ... thank you very much.
0
 
bbnp2006Commented:
Glad it worked out for you Dan.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now