HP EVA Cluster Extension Software Administrator Guide (5697-2445, July 2013)

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 Failover Cluster GUI, or Cluster CLI or
MMC, 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:
• For Windows Server 2008/2008 R2/2012, use the Failover Cluster GUI, or Cluster CLI or
MMC, 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 EVA Cluster Extension
Live migration is a managed failover of VM resources. Live migration must 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.
EVA Cluster Extension has the capability of discovering unfavorable storage-level conditions for
performing live migration. In response to these conditions, EVA Cluster Extension stops or cancels
the live migration process and informs 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, EVA Cluster Extension proactively cancels the live migration and informs 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 EVA 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 EVA array status to ensure a successful live migration.
The default StatusRefreshInterval value is 300 seconds. For more information about configuring
this property, see “Setting Cluster ExtensionEVA resource properties using a UCF” (page 36).
Using Hyper-V Live Migration with Cluster Shared Volumes is supported with EVA Cluster Extension.
TIP: For more information about using Hyper-V Live Migration with EVA 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
EVA Cluster Extension Software gives priority to storage system operations over cluster software
operations. If EVA 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
42 Configuring HP EVA Cluster Extension