3.6.0 MxFS for CIFS Administration Guide (5697-7082, December 2007)

Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 29
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
Timeout and Failure Severity: This setting works with the Virtual CIFS
Server policy (either
AUTOFAILBACK or NOFAILBACK) to determine what
happens when the monitors probe fails.
The default policies (
NOFAILBACK for the virtual host and
AUTORECOVER for the monitor) cause the ClusterPulse process to fail
over the Virtual CIFS Server to a backup node. The Virtual CIFS Server
remains on the backup node until a “healthier” node becomes available,
at which point the Virtual CIFS Server will fail over to that node.
You can use the Timeout and Failure Severity attribute to change the
failover/failback behavior. There are three settings:
NOFAILOVER,
AUTORECOVER
, and NOAUTORECOVER.
NOFAILOVER. When the monitor probe fails, the Virtual CIFS Server does
not fail over to a backup node. This option is useful when the monitored
resource is not critical, but is important enough that you want to keep a
record of its health. To use this option, you must also specify
IGNORE as
the Event Severity on the Scripts tab.