Need to replace an old 2003 domain controller.
The network currently consists of this server at one site, and two other servers at two other sites (both DC's also). So its the only server in the site, and I was thinking that virtualising it would give an extra layer of protection where the vhdx file could be backed up as a quick way to get things working in the even t of a disaster, but also use the standard backup tools from within the VM to get those granular file restores.
Also maybe even the old server could be used to host the VM if the new server explodes or something (slow but at least it will be running?)
So in this setup would it be better to just install full windows on the new hardware and add the hyperV role and then host the vm from inside there, or can you get away with just installing hyperV 2012 and then managing the VM remotely.
The current server is basically a DC and file / print / database server, was SBS but after moving to a hosted exchange service the local exchange services have been disabled.
Would I be better off making the physical server a DC and then having a separate file/print/db server as a vm inside it ?
Opinions ? I have only really used Virtualisation as test benches so far and have not really delved too deep into maintaining live systems on it.
thanks for your help
Gareth