Administrator's Guide

1. Create a cluster resource of resource type “Cluster Extension 3PAR for VM Management” in
the VM Role.
NOTE: Corresponding CSV is dependant on CLX.
Example: Using the PowerShell
Add-ClusterResource -Name VM_MGMT_Res -Group VM4_2k12 -ResourceType
"Cluster Extension 3PAR for VM Management"
2. Set the dependency of VM configuration resource on the newly created resource of resource
type “Cluster Extension 3PAR for VM Management”.
Example: Using the PowerShell
Add-ClusterResourceDependency -Resource VM_MGMT_Res -Provider
“Virtual Machine Configuration VM4_2k12”
The configuration is now complete and the VM role is enabled with VM management functionality.
Behavior of VM Management functionality in various disaster scenarios
This section describes various disaster scenarios and how the VM management functionality behaves
in these scenarios:
1. CSV disk owning cluster node and the VM owning cluster node are in different datacenter and
the VM Role is offline:
When user tries to bring the VM role online, the online operation fails as owner nodes of the
respective resource are running in different datacenters. Once the resource fails on the cluster
node, depending on the cluster role failover policies, the role behaves accordingly.
2. CSV disk owner node and the VM owner node are in same datacenter and the VM Role is
offline:
When user tries to bring the VM role online, the online operation succeeds as owner nodes
of the respective resource are running in same datacenters.
3. The cluster node which owns the CSV disk fails or the CSV disk fails and the CSV disk moves
to a node in the same datacenter or CSV disk is moved manually to a node in the same
datacenter:
In this scenario, since the CSV disk is moved to a node in the same datacenter, all the VMs
continue to run on their respective cluster nodes. There will not be any change in the ownership
for the VMs.
4. The cluster node which owns the CSV disk fails or the CSV disk fails and the CSV disk moves
to a node in the remote datacenter or CSV disk is moved manually to a node in the remote
datacenter:
In this scenario, all the VMs which are configured with CLX feature for VM management will
wait for the CSV disk to come online on a cluster node in the remote datacenter. Since the
CSV disk is moved to a node in the remote datacenter, all the VMs which are running in the
respective cluster nodes in the primary datacenter will be live migrated by CLX to cluster nodes
in the remote datacenter. Every role has next preferred node property. Selection of the target
node for the live migration will be based on how the next preferred owner property has been
set for the VM role.
Preferred Owners is not set: In this scenario, the next preferred owner node will be selected
randomly among the cluster nodes which are there in the remote datacenter. The selected
cluster node should be up. If not, search will continue until a cluster node is found in the remote
datacenter.
Preferred Owners is partially set: In this scenario, cluster nodes which are not part of the next
preferred owner node property, will be added to the list in the order of NodeID. Next preferred
owner which is in the same datacenter as the datacenter where CSV disk is owned will be
Virtual Machine Management hosted on a Cluster Shared Volume on Windows Server 2012 45