HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

365 of 739
message.
2. Dependencies—By default, the GeoCluster Replicated Disk resource is not
dependent on any other resources.
3. Policies—This tab controls how and when MSCS handles a failure of the
resource.
If resource fails, do no restart—Select this option if you do not want cluster
service to restart the resource if it fails.
If resource fails, attempt restart on current node—Select this option if you
want cluster service to restart the resource if it fails. Specify the length of time
to attempt restarts and the number of restarts to attempt during that period of
time.
If restart is unsuccessful, fail over all resources in this service or
application—If this option is enabled, the failure of the group will cause the
resource to move to another node. If this option is disabled, the failure of the
resource will not cause the resource to move to another node.
If all the restart attempts fail, begin restarting again after the specified
period—If this option is enabled, the cluster will delay the length of time
specified before trying to restart the resource again.
Pending timeout—This value determines how long the resource is allowed
to remain in a pending state before it fails. If the resource takes longer than
the time specified to be brought online or taken offline, the resource fails.
For more information on Policies options, see your Windows documentation.
4. Advanced Policies—This tab controls resource specific settings.
Possible owners—All nodes of the cluster are listed. Select or deselect the
nodes that you want to be possible owners.
If you add additional owners, the GeoCluster Replicated Disk resource
will connect the resource’s replication set to the new owners and begin
a mirror to each.
If you remove owners, the GeoCluster Replicated Disk resource will
disconnect the resource’s replication set from each owner removed.
The GeoCluster Replicated Disk resource must have at least two possible
owners to function properly.
Basic resource health check interval—This setting is formerly known as
the Looks Alive poll interval. It specifies how often the resource is polled to
determine whether it is still running on the active node. You can choose the
standard time period of 5 seconds, or you can specify your own value.
Thorough resource health check interval—This setting is formerly known
as the Is Alive poll interval. It designates how often the possible owners are