# “Saved-Critical” for Almost-Clustered Virtual Machines in Windows 2008 R2 Hyper-V

•
•
•
•
•
•

While staging a clustered Hyper-V environment this week, I ran into a head-scratching issue. After provisioning a few LUNs, masking them, and adding them as available storage to Failover Clustering, I began setting up the virtual machines on one of my cluster nodes. During maintenance, the physical servers were restarted. When I went back to continue configuring the virtual machines (which were not yet clustered at this point), I connected to the physical host on which I had been configuring them. While my other clustered virtual machines were running fine, the new ones that I had not yet finished configuring were in a “Saved-Critical” state.

I attempted to start them, but received an eror that the saved state could not be restored. I attempted to delete the saved state, but received an “Unable to perform operation” error. Additionally, I could not view the properties of the virtual machines in the Saved-Critical state.

I opened up Failover Cluster manager and noticed that the storage was now owned by the other cluster node. The problem is now obvious–the storage is no longer being presented to the host on which I was configuring the virtual machines. So, how to move these disks? Since the disks are marked “Available” (not having run through the new service Failover Clustering wizard to make the virtual machines highly available), I can’t move them by right-clicking on them and selecting a new node.

There is another solution, however, and it involves the cluster.exe command.

1. Open up a command prompt.
2. Run the following command:
cluster.exe GROUP "Available Storage" /Move

Voila! The disks moved back to the other node and the virtual machine state in Hyper-V manager changed from “Saved-Critical” to “Off.” I was then able to cluster the machines normally through Failover Clustering.