3.7.0 HP StorageWorks HP Scalable NAS File Serving Software administration guide - HP Scalable NAS 3.7 for Linux (AG513-96002, October 2009)

because the servers are equally healthy. If the failed service is then restored on
node 1, that node will now be healthier than node 2 and failback will occur.
(Note that if the virtual host policy was AUTOFAILBACK, failback would occur
when the probe failed on node 2 because both servers were equally healthy.)
• After the virtual host fails over to node 2, all service monitor probes fail on that
node. Node 1, with one down monitor, is now healthier than node 2, with three
down monitors, and failback will occur.
Failback policy and monitor probe severity
The following table shows how the virtual host failback policy interacts with the probe
severity setting for service and device monitors.
Behavior When Probe Reports DOWN
Monitor Probe
Severity
Virtual Host
Policy
Failover does not occur.NOFAILOVER
AUTOFAILBACK
Failover occurs. When service is restored, fail-
back occurs.
AUTORECOVER
Failover occurs and the monitor is disabled on
the original server. When the monitor is reen-
abled, failback occurs.
NOAUTORECOVER
Failover does not occur.NOFAILOVER
NOFAILBACK
Failover occurs. The virtual host remains on the
backup server until a “healthier” server is
available.
AUTORECOVER
Failover occurs and monitor is disabled on the
original server. The virtual host remains on the
backup server until a “healthier” server is
available.
NOAUTORECOVER
HP Scalable NAS File Serving Software administration guide 313