Came across this Post for an issue when adding a new node to and existing Hyper-V R2 SP1 cluster where the new node did not get added as a possible owner of the CSV disks or of the Quorum. The presenting symptoms for me was DPMs inability to backup VMs that resided on a particular node since the ownership of the CSV could not be transferred to a node that was not allowed as a possible owner.
Running Cluster Validation returns these warnings.
(Click Picture for Larger View)
For the Quorum, the change is easy. Just open the properties of the Quorum disk resource and on the Advanced Policies tab check the check mark next to the node to make it a Possible Owner.
(Click Picture for Larger View)
CSV disks this can be a bit more challenging however since you can not add or change the Possible Owner of a CSV from the GUI. Luckily you can do this using the CLUSTER.EXE utility as outlined in Gustavo’s Post.
CLUSTER.EXE . RES “Cluster Disk 1″ /ADDOWNER:<nodename>
You could also use a PowerShell command to do the same thing.
- Open PowerShell
- Load the FailoverClusters Module
- Import-Modules FailoverClusters
- Run the Set-ClusterOwnerNode command:
- Get-ClusterResource "Cluster Disk 1" | Set-ClusterOwnerNode -Owners <nodename>
Looking at the Cluster Validation report again now will show that there are no problems with incomplete disk ownership.
(Click Picture for Larger View)
VirtuallyAware 