HP XP Cluster Extension Software Administrator Guide

2. Remove the cluster disk dependency on the CLX resource.
Cluster.exe resource <Disk Name> /REMOVEDEP:<CLX Resource Name>
Example: cluster resource "Cluster Disk 1" /removedep:"CLX_XP_Cluster
Disk 1”
3. Remove the cluster resource
Cluster.exe resource <DiskName> /delete
Example: cluster resource " CLX_XP_Cluster Disk 1" /delete
For more information on deleting resources, see your Microsoft documentation.
Using Hyper-V Live Migration with HP XP Cluster Extension
Live migration is a managed failover of VM resources. Live migration should be performed when
all of the solution constituents are in a healthy state, all the servers and systems are running, and
all the links are up. Ensure that the underlying infrastructure is in a healthy state before performing
live migration.
HP XP Cluster Extension has the capability of discovering unfavorable storage-level conditions for
performing live migration. In response to these conditions, HP XP Cluster Extension stops or cancels
the live migration process and informs you. This is accomplished with no VM downtime. For
example, if live migration is initiated while VM data residing on the storage arrays is still merging
and not in sync, HP XP Cluster Extension proactively cancels the live migration and informs you to
wait until the merge is in progress. Without this feature, live migration might fail or the VM might
come online in the remote data center with inconsistent data.
The HP XP Cluster Extension StatusRefreshInterval property, which you can configure in a UCF for
each application, specifies the time interval between consecutive array status gathering operations
before the live migration to the target cluster node occurs. By adjusting this property, you can
increase the probability of getting the correct XP array status to ensure a successful live migration.
The default StatusRefreshInterval value is 300 seconds. For more information about configuring
this property, see “Setting HP XP Cluster Extension properties using a UCF” (page 34).
HP XP Cluster Extension cancels live migration operations within the local data center when the
device/copy group is not in PAIR status. Use the LocalDCLMForNonPAIRDG property, which can
be configured in a UCF for each application, to change the setting to allow live migration to occur
within the local data center even if the device/copy group is not in PAIR status.
Hyper-V Live Migration is supported with HP XP Cluster Extension for Windows Server 2008 R2
and Windows Server 2012/2012 R2 using only the synchronous fence levels DATA and NEVER.
The asynchronous and journal fence levels are not supported.
Using Hyper-V Live Migration with Cluster Shared Volumes is supported with HP XP Cluster Extension.
TIP: For more information about using Hyper-V Live Migration with HP XP Cluster Extension, see
the white paper Live Migration across data centers and disaster tolerant virtualization architecture
with HP Cluster Extension and Microsoft Hyper-VTM on the white papers website: www.hp.com/
storage/whitepapers.
Timing considerations for MSFC
HP XP Cluster Extension gives priority to disk array operations over cluster software operations. If
HP XP Cluster Extension invokes a disk pair resynchronization operation or gathers information
about the remote disk array, HP XP Cluster Extension waits until the requested status information
is reported. This ensures the priority of data integrity over cluster software failover processes. This
behavior can lead to failed HP XP Cluster Extension resources as described below:
• HP XP Cluster Extension uses RAID Manager instances to communicate with the remote disk
array. Depending on the setting of the RAID Manager instance timeout parameter and the
Using Hyper-V Live Migration with HP XP Cluster Extension 41