So let’s say I have a SBS 2008 that is running in a HyperV server. It’s a child inside the parent. And I’m looking for the most officially supported backup and restore solution on the face of the planet? One that if I called Microsoft support they would do their best to ensure that I could get myself back to where I was? What would that be exactly?
The answer is, ensuring that you used the native SBS 2008 backup and park it out to a vhd drive.
Why is this the most supported? Because that’s the official backup solution that you can see in the SBS 2008 documentation and thus the Engineers will be the most trained and well equiped to guide you in a restore using that method.
Now what about backing up the parent and having it VSS aware so that the Parent backs up the child? Will the support folks at Microsoft refuse to help? The answer is no, but the reality is that they can only do best effort support in this scenerio. We are after all virtualizing a domain controller. As long as we stay with one domain controller, we actually have a better chance of having no issues. It’s when there are multiple domain controllers that tombstone values and what not come into play. At the end of the day the best code to restore an active directory information is the system state backup that is made as part of the sbs backup process.
This same “best support effort” holds true when you use third party backup solutions. Microsoft can’t hold your hand if you are using another product that they don’t know how it works. If your only backup is a third party backup program, you’ll need to go through them, not Microsoft for your support.
Backup and Restore Considerations for Virtualized Domain Controllers: