Administrator's Guide

To bring resources online:
• Use Failover Cluster GUI or Cluster CLI or Microsoft PowerShell Cmdlets.
• For Server Core or Hyper-V Server, use the CLI or the MMC or Microsoft PowerShell Cmdlets.
For more information on using this command, see your Microsoft documentation.
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:
• Use Failover Cluster GUI or Cluster CLI or Microsoft PowerShell Cmdlets.
• For Server Core or Hyper-V Server, use the CLI or the MMC or Microsoft PowerShell Cmdlets.
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:
• Use Failover Cluster GUI or Cluster CLI or Microsoft PowerShell Cmdlets.
• For Server Core or Hyper-V Server, use the CLI or the MMC or Microsoft PowerShell Cmdlets.
• For more information on deleting resources, see your Microsoft documentation.
Using Hyper-V Live Migration with HP 3PAR 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 3PAR Cluster Extension has the capability of discovering unfavorable storage-level conditions
for performing live migration. In response to these conditions, HP 3PAR 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 system is still
merging and not in sync, HP 3PAR Cluster Extension will proactively cancel the live migration and
inform the user to wait until the disks are fully in sync. Without this feature, live migration might
fail or the VM might come online in the remote data center with inconsistent data.
The HP 3PAR 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 HP 3PAR storage system status to ensure a
successful live migration. The default StatusRefreshInterval value is 300 seconds. For more
information about configuring this property, see “Setting HP 3PAR Cluster Extension properties
using a UCF” (page 34).
TIP: For more information about using Hyper-V Live Migration with HP 3PAR Cluster Extension,
see the white paper Live Migration across data centers and disaster tolerant virtualization
architecture with HP StorageWorks Cluster Extension and Microsoft Hyper-V on the white papers
website: www.hp.com/storage/whitepapers.
40 Configuring HP 3PAR Cluster Extension