Hyper-V - All our virtual servers won't start........ please help

[pritchardavid]

Ok seems our Hyper-V host servers have restarted due to updates I think. The Hyper-V hosts servers are setup on a SAN (Intel MFSYS25 with SAN key activated) for the storage for the Hyper-V, With the cluster feature installed on each host to enable the SAN to work. Now i'm assuming that because all servers have been restarted the DC were also shut down, i'm guessing that the cluster feature needs a DC to authenticate between the cluster group (Hyper-V host servers). I cannot open the cluster storage folder nor can the virtual server access the storage folder either. What the next best thing to try? many thanks in advance

[RabbieBurns]

do you have a physical DC or is your DC virtualised on the SAN?

[morganw]

This may be appropriate:

HYPER-V and SYSTEM CENTER: Why You Should Not Running Domain Controller in a Cluster Hyper V Host?

[pritchardavid]

Ok have managed to pull a vm image from the san (opened it from disk management, properties or the hard drive, then finding the volume) otherwise would have used a backup from a few days ago....

 

Regarding physical, my plan, once all the virtual servers moved over the san, was to place a another virtual dc on another server (Our backup DPM physical server) I can't physically install it on the DPM because your not meant to install it on a server with SQL..... The backup server is not on a san, so i'm guessing that should be fine?

 

Need to make sure the other guys don't restart any hyper v host servers until we get a third dc running on the other server.

Edited March 14, 2012 by pritchardavid

[MrWu]

Hi

 

Good luck and hope ypu get it all working.

 

We will be having a similar setup soon with an Intel MFSYS25 with 3 x modules with Hyper V. We are planning to use one server module as a hardware failover and leave out Hyper V clustering.

 

How are you finding the performance of your server network and disk performance wise with VMs?

 

Cheers