HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)

Chapter 16: Configure Service Monitors 200
monitored resource is not critical, but is important enough that you want
to keep a record of its health.
AUTORECOVER. This is the default. The virtual host fails over when a
monitor probe fails. When the service is recovered on the original node,
failback occurs according to the virtual host’s failback policy.
NOAUTORECOVER. The virtual host fails over when a monitor probe
fails and the monitor is disabled on the original node, preventing
automatic failback. When the monitor is reenabled, failback occurs
according to the virtual host’s failback policy.
The
NOAUTORECOVER option is useful when integrating HP Clustered
File System with a custom application where certain application-specific
actions must be taken before the failback can occur.
For more information on the interaction between the Timeout and Failure
Severity attribute and the virtual host failback policy, see “Virtual Hosts
and Failover” on page 185.
To set the Timeout and Failure Severity attribute from the command line,
use the following option. (Note that this option is case-sensitive.)
--probeSeverity nofailover|autorecover|noautorecover
Service Priority
The service priority is used by HP Clustered File System when it fails
over services. Service priorities are natural numbers, with 0 (zero)
representing the highest priority and higher numbers representing lower
priorities. If multiple failures prevent HP Clustered File System from
placing a virtual host on a server where all of its associated services are
available, HP Clustered File System next looks for a server where the
associated service with the highest priority is available. By default, all
service monitors have a priority of 0.
To set the Service Priority from the command line, use this option:
--priority <priority>