Link to home
Start Free TrialLog in
Avatar of IanTh
IanThFlag for United Kingdom of Great Britain and Northern Ireland

asked on

migrating a dc into esx4 vcenter

HI Guys

Whats the best practice when migrating a dc or any other important server using VMware converter standalone

is it best to do a p2v with standalone converter I have heard that sometimes this method fails or
is it best to do a backup, create the sever in esx and restore the backup onto the new dc in esx

or another way

 
Avatar of Brett Danney
Brett Danney
Flag of South Africa image

All my physical servers I did a P2V. Once done I shutdown the physical (kept it for a week or two as a backup) ran the server as a virtual and if there were no issues carried on. Out of about 150 servers I had an issue with two that resulted in the physical having to be restarted and the VM trashed. Both were a result of massive harddisks that failed to import.
Avatar of jacques_vivier
jacques_vivier

I'm not sure what the best practice is, but I have used the standalone converter on numerous DC's without any problems. On exchange or SQL servers do I stop the service, just incase a users wants to do something while I'm busy.
If you want to migrate a DC I'd suggest du install a new server within the ESX-Server and promote it with dcpromo.

Afterwards migrate the FSMO roles to the new server (if the old one hold them) and demote the old server with dcpromo and remove it.

If you're going this way you need to make sure that all other application on this server are migrated.

Another option would be to use an offline P2V for the System and have a look what happens afterward.
Most of the time I try do migrate the DC with normal migration (option 1)

If you need to do P2V because there are many other features or applications make a System State Backup before you start that you're able to recover the Active Directory if it fails, what might be the biggest risk. In most cases don't see any problems with other features e.g. file service.
Regardless of the server you're wanting to virtualize, VMware's *official* stance is to always create a new VM, then add and/or restore data to it to get your physical to virtual. That being said, I have converted all my DCs and have had no to minimal issues.
Here are some pertinent links you should reference:
http://kb.vmware.com/kb/1006996
And, from MS:
http://support.microsoft.com/kb/888794

And previous EE post on the subject:
https://www.experts-exchange.com/questions/25127747/Installing-DC-on-Virtual-Machine.html

Regards,
~coolsport0
Avatar of IanTh

ASKER

so if you virtualize a dc and it fails then as its a copy you can do a backup then virtualize it or if its better do the backup first yes and then p2v yes so if it fails i can create a new vm and then restore the backup and then create all the server rolls?
SOLUTION
Avatar of coolsport00
coolsport00
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You can also Google "Authoritative restore" and you will come across a MS KB that explains it in greater detail.

~coolsport00
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial