Disk2VHDX Active Directory Server 2008 / 2012 (Converting physical AD DC Server to Hyper-V Virtual Machine)
Greetings,
I am looking for the necessary detailed steps to take prior to converting my physical Active Directory Server/Domain Controler to a Hyper-V Virtual Machine.
I want to be able to create my Hyper-V VM , Attach the VHDX, and be up and running as soon as possible in the event of a Server failure.
I have successfully created bootable Server 2008 and Server 2012 VM's, but each VM brings up a "Directory Services Restore Mode" prompt prior to allowing me to log into the newly created VM.
I would like to avoid DSRM all together.
Thank you in advance.
I am looking for the necessary detailed steps to take prior to converting my physical Active Directory Server/Domain Controler to a Hyper-V Virtual Machine.
I want to be able to create my Hyper-V VM , Attach the VHDX, and be up and running as soon as possible in the event of a Server failure.
I have successfully created bootable Server 2008 and Server 2012 VM's, but each VM brings up a "Directory Services Restore Mode" prompt prior to allowing me to log into the newly created VM.
I would like to avoid DSRM all together.
Thank you in advance.
Cliff Galiher
Is this a disaster recovery plan or are you trying to migrate? Either way, disk2vhdx is not the right path. But knowing your intent can help experts give you the proper advice to meet your goals.
ASKER
Thanks for responding Cliff - Basically for DR.
I have about 15 physical Servers in different locations that already have local System images saved to a local NAS box.....as well as remote off-site data backups.
What I don't have are air gaped System image Backups.....so the purpose is to create a monthly Server System Backup image to a USB drive of each Server using Disk2VHD and keep them off the network in case those local System image backups become unusable i.e. Ransomware.
About a year ago one of the Servers go hit with Ransomeware which encrypted all NAS and USB backup drives on the network. Our data was fully restored from the remote backup but we did have to rebuild the system from scratch.
We have a physical Server with Hyper-V ready to run a Hyper-V VM to get us up and running until we decide on a permanent Server solution.
I am looking for something simple,cheap and effective to accomplish the above described task.
I hope this clarifies my request.
Thanks.
I have about 15 physical Servers in different locations that already have local System images saved to a local NAS box.....as well as remote off-site data backups.
What I don't have are air gaped System image Backups.....so the purpose is to create a monthly Server System Backup image to a USB drive of each Server using Disk2VHD and keep them off the network in case those local System image backups become unusable i.e. Ransomware.
About a year ago one of the Servers go hit with Ransomeware which encrypted all NAS and USB backup drives on the network. Our data was fully restored from the remote backup but we did have to rebuild the system from scratch.
We have a physical Server with Hyper-V ready to run a Hyper-V VM to get us up and running until we decide on a permanent Server solution.
I am looking for something simple,cheap and effective to accomplish the above described task.
I hope this clarifies my request.
Thanks.
Disk to VHD is not supported method for virtualized DC's when u have multiple physical DC's
Also keeping virtual dc in shutdown mode as standby is also not supported
It will born new issues like lingering objects, USN ROLLBACK, sushil and ad replication issues, normal wrap etc
The supported method is to deploy virtual dc properly by promoting additional domain controller and keep it online
Also keeping virtual dc in shutdown mode as standby is also not supported
It will born new issues like lingering objects, USN ROLLBACK, sushil and ad replication issues, normal wrap etc
The supported method is to deploy virtual dc properly by promoting additional domain controller and keep it online
Use Microsoft Virtual Machine Converter... see my EE Articles to assist you..
HOW TO: P2V, V2V for FREE to Hyper-V - Microsoft Virtual Machine Converter 3.1
HOW TO: Convert a physical server or virtual server (P2V/V2V) to Microsoft Hyper-V using Microsoft Virtual Machine Converter 3.1
HOW TO: P2V, V2V for FREE to Hyper-V - Microsoft Virtual Machine Converter 3.1
HOW TO: Convert a physical server or virtual server (P2V/V2V) to Microsoft Hyper-V using Microsoft Virtual Machine Converter 3.1
make sure:
You can take the domain controller offline by stopping the NTDS service or by restarting the computer in Directory Services Restore Mode (DSRM). And the computers must remain offline during the P2V migration.
One more thing, to prevent issues with Active Directory replication, do not bring the physical source machine back onto the network again before you reformat the hard disk.
You can take the domain controller offline by stopping the NTDS service or by restarting the computer in Directory Services Restore Mode (DSRM). And the computers must remain offline during the P2V migration.
One more thing, to prevent issues with Active Directory replication, do not bring the physical source machine back onto the network again before you reformat the hard disk.
https://technet.microsoft.com/en-us/library/virtual_active_directory_domain_controller_virtualization_hyperv%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
This will give you better idea how you can plan for DC server P2V migration to avoid DSRM.
This will give you better idea how you can plan for DC server P2V migration to avoid DSRM.
As an earlier commenter said, there are issues with using disk2vhdx for DR. I cant recommend it. You'd be much better of using a backup program or at the very least doing a scheduled task and rotating media out as procedure. You'll find restoring your network from your plan won't work as expected, and the WORST time to discover problems is when you are in an emergency outage situation.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks all for commenting - All your contributed information makes sense.....the problem is that these 15 locations are small businesses with only one physical Server acting as a AD DC File Server with 10 workstations or less and currently no virtualization in the infrastructure.
These 15 locations are the last locations who still depend on a physical Server as the AD DC File Server - When the time is right they too will be migrated to a virtualized Hyper-V environment consisting of a AD DC VM and separate File Server VM.
It sounds like my planned direction is a gamble at best.
After reading all the contributed information it appears this is the best solution:
(I am asking….not inferring)
1) Create a backup AD DC Hyper-V VM Server and keep it off line.
2) Daily off-site backup of the AD data.
3) When/if the physical AD DC Server fails – bring the backup AD DC Hyper-V backup VM Server on-line and restore AD data via DSRM
This solution is cumbersome and time consuming at best but it sounds like anything less than the 3 steps above will
in effective.
These 15 locations are the last locations who still depend on a physical Server as the AD DC File Server - When the time is right they too will be migrated to a virtualized Hyper-V environment consisting of a AD DC VM and separate File Server VM.
It sounds like my planned direction is a gamble at best.
After reading all the contributed information it appears this is the best solution:
(I am asking….not inferring)
1) Create a backup AD DC Hyper-V VM Server and keep it off line.
2) Daily off-site backup of the AD data.
3) When/if the physical AD DC Server fails – bring the backup AD DC Hyper-V backup VM Server on-line and restore AD data via DSRM
This solution is cumbersome and time consuming at best but it sounds like anything less than the 3 steps above will
in effective.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you all for contributing your knowledge and expertise - I'm sure you have all saved me a headache!
Unfortunately current resources don't facilitate creating/implementing a 2nd AD DC on the network - physical or virtual.
Using Disk2VHD to create a "backup" image copy of an Active Directory/Domain Controller is off the table.
I will test Andrew's idea of utilizing Veeam's free Backup product and go from there.
Thank all again - I appreciate your time.
John B
Unfortunately current resources don't facilitate creating/implementing a 2nd AD DC on the network - physical or virtual.
Using Disk2VHD to create a "backup" image copy of an Active Directory/Domain Controller is off the table.
I will test Andrew's idea of utilizing Veeam's free Backup product and go from there.
Thank all again - I appreciate your time.
John B