HP P6000 Cluster Extension Software Administrator Guide (5697-2274, November 2012)

Taking a resource offline
Resources are usually taken offline automatically when the service or application is taken offline.
Taking a resource offline causes resources that depend on that resource to go offline.
When taking resources offline:
• For Windows Server 2008/2008 R2/2012, use the GUI, MMC, or CLI.
• For Server Core or Hyper-V Server, use the CLI or the MMC.
For more information on using this command, see your Microsoft documentation.
Deleting a resource
Deleting a running resource causes the resource and its dependents to go offline.
CAUTION: Deleting a running resource does not remove the resource_name.online file.
When deleting resources:
• For Windows Server 2008/2008 R2/2012, use the GUI or CLI.
• For Server Core or Hyper-V Server, use the CLI or the MMC.
For more information on deleting resources, see your Microsoft documentation.
Using Hyper-V Live Migration with P6000 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.
P6000 Cluster Extension has the capability of discovering unfavorable storage-level conditions for
performing live migration. In response to these conditions, P6000 Cluster Extension will stop or
cancel the live migration process and inform the user. 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, P6000 Cluster Extension will proactively cancel the live migration and
inform the user 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 P6000 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 P6000 array status to ensure a successful live
migration. The default StatusRefreshInterval value is 300 seconds. For more information about
configuring this property, see “Setting P6000 Cluster Extension properties using a UCF” (page 33).
Using Hyper-V Live Migration with Cluster Shared Volumes is not supported with P6000 Cluster
Extension.
TIP: For more information about using Hyper-V Live Migration with P6000 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 MSCS
P6000 Cluster Extension Software gives priority to storage system operations over cluster software
operations. If P6000 Cluster Extension is invoked during a DR group member resynchronization
operation (merging) or is gathering information about the remote storage system, it waits until the
requested status information is reported. This ensures the priority of data integrity over cluster
38 Configuring P6000 Cluster Extension