Search This Blog

Friday, August 12, 2011

Recover Domain Controller Virtual Machine Inside CSV When Hyper-V Failover Cluster Failed


Well, first of all. I would like to apologies on posting wrong information about “Caution When Remove CSV”. The previous blog post has deleted and i would like to take this opportunities to Thanks “Vincent Hu” which highlighted that he had tested this scenario on Hyper-V Failover Cluster without destroying the data on the LUN. Yup, he is right.

No data is loss after remove the CSV. Here is the re-post of blog to recover a Virtual Machine especially when we have deploy domain controller into CSV.

Note:- It is still not recommended to put DC into CSV unless we have another DC running on physical/ not in CSV.

Workaround to take back DC VM from CSV.

1. At this moment , your cluster has offline and failed due to cannot connect to Domain Controller.
2

2. Go to Cluster Shared Volume, select the Cluster volume which contained the VHD. (Previously i took the Volume 1(which is empty, that has caused a false alarm, sorry)
1

3.Offline the resources, right click and select Remove from Cluster Shared Volumes.
3

4. Once remove, go to Storage and you will see the disk located in Available Storage. Assign a Drive Letter and copy the VHD out.

4

This is the simple trick to recover the DC VM which is inside the CSV. Hope now you can create the VM Configuration and start the Domain Controller. Once the DC is up, then you will be able to start the Hyper-V Failover Cluster.

Just to remind again, you should have at least 1 DC not in CSV or run in physical server.

Good luck…

2 comments:

  1. If the cluster service isn't started, you cannot work on CSV and other resources. I'm right now in that situation... Do you know a way to force the cluster to start and recognize the CSVs???

    ReplyDelete
    Replies
    1. not really. have tested few but not available. Another way is try to access cluster by connect using . (dot). You can break the CSV and take out the DC VM. Re-create VM configuration and boot up the cluster

      Delete