Backup / restore domain controller

[LinkeLoe]

Hi,

I know this question has been asked several times, but I cannot find a suitable answer...

We are using Veeam B&R 6.1 for Hyper-V and I was wondering how to backup and restore a domain controller with Veeam. In the backup job I have checked the box "application aware image processing" and I filled in the correct domain credentials. The backup is running successfully. I also get no errors in restoring a domain controller (to our test environment).

I understand that the first time the server is booting, it should go into DSRM, but this doesn't happen. When I first boot the VM, I see a screen with the option to start Windows normally, or boot into safe mode, the default is to start Windows normally. It never boots into DSRM automatically. It takes a long time to boot the VM and when I'm finally able to login and start DNS manager, or anything related to Active Directory, I get error messages of domain naming information that cannot be found...

What is the correct way to backup and restore a virtual domain controller, running on Hyper-V?

[Vitaliy S.]

Hi Leo,

It doesn't really matter what hypervisor you're using to host your DC VM, as the restore procedure looks exactly same for both platforms. If you do not see this behavior for some reason, then it would be best to open a support case and let our support engineer investigate it for you.

Thanks!

[jlyle]

I am getting the same issue as you LinkeLoe, I am running 6.1 with VMware and a surebackup of my 4 DC's results in the message "The domain ..name here... could not be found because: The specified comain either does not exist or could not be contacted." when accessing tools like AD users and computers snap in.

Connectivity between the DC's is not a problem (pingable by ip and name), DNS appears to be functioning correctly.

Please let me know if you find a solution, I'll get back with anything I can find.

[Gostev]

LinkeLoe or jlyle could please either of you post the support case ID for this issue, so I can check up on this with R&D. Thanks!

[jlyle]

I just opened a support case yesterday and have started working with them on a resolution ( ref:_00D30RWR._50060NugB6:ref). Thanks

[Gostev]

( ref:_00D30RWR._50060NugB6:ref)

This is not a support case ID. Look for 8 digit number.

[jlyle]

My apologies the case number is 00173386 I have just been escalated to tier 2.

[jlyle]

In my case the domain controllers were not always starting quick enough. The Resolution was to ensure that the correct roles were selected on the role tab of the VM's in the application group increasing the boot timeout to 1800s and application timeout to 600s, and ensuring that on the test scripts tab that only comain controller script is running. Loosing the other scripts ensures that surebackup jobs wait around for less time otherwise I would need a larger application timeout.

Only other thing is that our Exchange 2007 Store service did not always start automatically, probable resolution to set the service on delayed start.