This is a pretty old page - 3yrs. A lot has probably change at VMWare in that time + they have a HUGE/complicated environment which is evident from the fact they have a need for 48 DCs lolpush3r wrote:
I understand that virtualizing all DC would make life a lot easier, but what if one of Veeam's customers has a need for a physical DC? And did you know that even VMWare has one Physical DC in their environment?
source: http://www.ballblog.net/2010/12/do-you- ... omain.html
"Once again, there is no right or wrong answer to virtualizing your domain controllers though you may find it interesting, as I did, that VMware has a 48 DCs, 47 are virtual and 1 is physical. The physical domain controller is the Forest PDC emulator. "
If your not prepared (for what ever reason) to VM your DC1, then i would agree too that putting a VM DC (3rd DC) into your DR environment will also greatly help with your recovery....but its not going to solve all your problems.
In a disaster where your main site is taken out 100%, you will still lose DC1 and never get it back. When you fail over to your DR site, your AD will still be messed up and require manual cleaning/clearing of DC1 to get everything right again. Not impossible to do, but it is a mess all the same....something you could avoid completely/easily.
Creating a new VM DC and leaving a DC physical is going to make things more complicated in your environment than just taking the one single action of VMing DC1. Your adding a 3rd DC unnecessarily and your strapping a DC to physical hardware for no real reason which results in that DC losing DR ability.
The chicken/egg/dns issues apply only to exceptional setups - i am pretty sure you could identify if you would have any of those issues....rule them out. When all of my VMs are down including the DCs (say for a planned total power down event) - when i bring the hosts back online, its true, i have no DNS.....i rely on IP addresses to get to the hosts to bring vcentre and the DCs back online....but once they are up - all is back to normal and i can use host/dns names.
My DCs VMDKs live on the same shared storage (raid 10, dual controllers etc all the redundant bits)....and thanks to veeam, i replicate all my VMs to a totally separate host with totally separate storage so can bring all that online in minutes if my primary hosts/storage fails spectacularly together......veeam also backs everything up to another local totally separate store.....AND veeam also backs everything up over the WAN to a location 100 miles away. You dont NEED to have your DC VMDKs on separate storage if your primary storage is reliable/good + you leverage veeam properly to protect your environment from the very rare major disasters we are talking about here.
Sry for commenting on this again (just trying to help) - its completely your choice of course but i do believe you could greatly improve your DR ability by taking a different action than the one your planning to. VM DC1 - all your problems are solved (except for the alien thing )