Sun, Aug 19 2012 9:08
Where does your DC go?
So where should be your DC in a virtual machine setup?
Should you do snapshots of virtual machines?
For the first - I've been told never ever ever do a domain controller that has the hyperV role. But when I went looking for info on how this is not supported - I'm finding blog posts that are more wiggly - http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/11/24/the-domain-controller-dilemma.aspx
In my office I'm using the parent as a workgroup. So that it's independent of the domain. One item of note in that blog post is the statement that if you have the dc role and the HyperV role together, you need to shut down the HyperV children before rebooting the box. Right now in my workgroup mode, when I patch I don't. I just reboot the box, the hyperV does a 'saved state' and then turns back on when done.
"You should never use saved state / snapshots with domain controllers - as this can be catastrophic"
Yet that post indicates that saved state is a no no? Mind you I only have one Domain controller so that the issue of tombstoning won't occur.
I do not take snapshots on domain controllers, nor on my real HyperVs. I've taken a snapshot on my test box and accidentally put the snapshot files in a small size drive and ran the drive out of room. This in turn paused the child machines. Thus I'm not comfy with snapshots on real virtual machines for fear of my stupidity kicking in.
I'll be adding some of these comments to the HyperV for SMB build doc.
Filed under: HyperVServer