This is a lab not in production.
We've been testing the Hyper-V cluster recently. two Windows 2008 R2 SP1 servers are running Hyper-V in a cluster (2 SAN)
Another Hyper-V is in standalone.
One DC is in the cluster
One DC is running on the standalone Hyper-V
One DC is running on a physical server.
The goal was to see if we can also power it on (after the shut down) in the event that a DC goes down. So we moved all FSMO roles on the DC in the cluster (which of cource can't be brought online before the cluster is online)
We shuted down all VM and servers,
Then we powered on the DC from the physical server. Then the standalone Hyper-V. we couldn't login to the domain at first.
We powered on the other DC running on the standalone Hyper-V.
It looks like AD has some trouble to run without the DC that had all the FSMO roles.
Then we powered on the Hyper-V cluster. The cluster failed to go online. it couldn't resolve the cluster name (but the IP was online) Besides, it looks like one of the Hyper-v that had all the disks (SAN) online was the one having the problem.
As soon as we shut it down, the disks ownership has been transfered to the other Hyper-V and everything went back online.
As far as I understand. It can take more time to bring all AD ressources online when the DC that holds all FSMO roles is down. Is that true?
Besides, when one of the Hyper-V in the cluster is having trouble to reach the DNS, the cluster cannot be used from the IP only. But I can be wrong here. Please let me know
The disks (SAN) owned by a Hyper-V server will not be available if this server is having problem to communicate with the DNS, although all other DC are also running the DNS,
Thanks for your feedback