- Two server Hyper-V cluster server with Windows 2008.
- One SAN disk Cluster drive for the virtual file server storage virtual hard disk.
- One SAN disk Cluster drive for the operating system virtual hard disks and virtual machine configurations.
In Failover Cluster Management under Services and Applications there is a Service / Application group Virtual Machines. In this group all the Hyper-V Virtual Machines are added. One SAN Cluster Disk G: is added to this group for storage of all the virtual hard disks and virtual machine configurations. The File server has its own Cluster Disk E: for the file server storage virtual hard disk. The operating system disk and the virtual machine configuration of the File Server resides on the other SAN Cluster drive G:, together with all the other virtual harddisks of the other virtual machines. E: is listed in Failover Cluster Management / Storage under Available Storage. Cluster Drive G: is connected to the Virtual Machines Services and Applications group.
During a fail over or a move of the virtual machines to the other node, the File Server storage Cluster Drive E: doesn't move to the other node. The Virtual Machines and G: the main Cluster Drive do move to the other node. This results in a File Server that fails to start on the active cluster node. After rebooting the passive cluster node, the E: custer drive is moved, forced to the active cluster node and the file server can be successfully started.
It has worked before, suddenly is doesn't anymore. Something or someone must have changed something on the server. What could be the reason that the File Server cluster disk doesn't move to the other cluster server?
I'm not sure, should the disk be added to the Virtual Machine Services and Applications for it to move to the other cluster? Or could adding this disk to the Virtual Machine Services and Applications result in any other error?