4.1.0 HP PolyServe Matrix Server administration guide (T5392-96073, October 2010)

• AUTORECOVER. The virtual host fails over when a monitor probe fails. When
the service or device 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
Select a backup interface for failover
When ClusterPulse needs to fail over a virtual host, it determines the best network
interface to receive the virtual host. It bases its decision on the status of the available
backup interfaces and their underlying servers. Typically, it looks for an “up” network
interface where all services are “up” on the underlying server.
You can use the following Advanced settings to affect how ClusterPulse selects the
network interface for failover.
• The Event Severity setting allows you to specify whether ClusterPulse should con-
sider the existence of monitor events (such as a script failure or timeout) when it
selects a network interface for failover. If the events are considered, the network
interface for the affected server becomes less desirable.
• For service monitors, you can assign a priority to each monitor (the Service Priority
setting). If ClusterPulse cannot locate an interface where all services are “up” on
the underlying server, it selects an interface where the highest priority service is
“up” on the underlying server.
Specify failback behavior of the virtual host
When you configure a virtual host, you can specify the failback action that the virtual
host will take following a failover to a backup server. There are two options:
AUTOFAILBACK and NOFAILBACK.
AUTOFAILBACK is the default for virtual hosts. HP PolyServe Software for Windows
File Serving and HP PolyServe Software for Microsoft SQL Server provide entities
similar to virtual hosts (Virtual File Servers and Virtual SQL Servers). These entities
use NOFAILBACK as the default.
AUTOFAILBACK
AUTOFAILBACK is intended to return the virtual host to its original configuration, or
as close to it as possible. After the virtual host fails over to a backup server,
ClusterPulse watches the health of the servers higher in the list for that virtual host.
HP PolyServe Matrix Server 4.1.0 administration guide 199