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

software failover behavior. However, this behavior can cause a failure of P6000 Cluster Extension
resources in some cases.
• When P6000 Cluster Extension uses HP SMI-S to communicate with the HP P6000/EVA
storage system, depending on the settings of the SMI-S request timeout property and the number
of retries, the online operation could time out. This can occur if the list of management servers
is populated with many management servers and the P6000 storage system is busy processing
other management commands.
• When a DR group member resynchronization (merge) is in progress, the software waits until
the DR group is in a normal state if the ApplicationStartup resource property is set to
RESYNCWAIT. In case of merge/resynchronization, the delta data (stored in the history log)
between the source and destination vdisks could be large enough for the copy process to
exceed the resource PendingTimeout value.
• The values of the ResyncWaitTimeout and DataSyncTimeout properties must be less than the
configured resource PendingTimeout value.
In general, because the failover environment is dispersed into two (or more) data centers, the
failover time cannot be expected to be the same as that in a single data center with a single shared
disk device. Therefore, the following values of the P6000 Cluster Extension resource and the service
or application using that resource, must be adjusted, based on failover tests performed to verify
the proper configuration setup: FailoverPeriod, RestartPeriod, PendingTimeout, LookAlive, and
IsAlive.
In addition, the service or application's FailoverPeriod value must be higher than the resource's
RestartPeriod value and both must be higher than the resource's PendingTimeout value.
Microsoft Cluster Server provides two properties to adjust state change recognition/resolution:
• IsAlive
• LookAlive
The software automatically calls the IsAlive function whenever the cluster service calls the LookAlive
function. Therefore, both functions must be set to the same value.
NOTE: For Windows Server 2008/2008 R2/2012, the IsAlive and LookAlive properties are
replaced by the Thorough Resource Health Check Interval and Basic Resource Health Check Interval
properties.
Bouncing service or application
P6000 Cluster Extension will alternate (start and fail) between local nodes if the ApplicationStartup
property has been set to FASTFAILBACK and no remote system is available until the service or
application restart limit has been reached. For more information, see “APPLICATION
objects” (page 45).
Administration
P6000 Cluster Extension administration includes remote management of resources and monitoring
of system resources and logs.
Remote management of P6000 Cluster Extension resources in a cluster
You can use the MMC with Failover Cluster Management to manage clusters and configure P6000
Cluster Extension resources. Note the following when configuring P6000 Cluster Extension resources
by using the MMC from a remote management station:
• When you use the MMC to remotely configure P6000 Cluster Extension resource properties
in a Server Core or Hyper-V Server cluster node, the Failover Cluster Management GUI on
the remote management station displays the standard Microsoft Properties tab instead of the
Bouncing service or application 39