3.1.2 MxFS-Linux Administration Guide

Chapter 2: Configure Export Groups 24

The default policies (AUTOFAILBACK for the Virtual NFS Service and

AUTORECOVER for the high-availability monitor) cause Matrix Server to

fail over the associated Virtual NFS Services to a backup network

interface on another node when the monitor probe fails. When the NFS

service is restored on the original node, Matrix Server fails back the

Virtual NFS Services to the network interfaces on the original node.

You can use the Probe Severity attribute to change this behavior. There

are three settings for Probe Severity:

NOFAILOVER, AUTORECOVER, and

NOAUTORECOVER.

NOFAILOVER. The Virtual NFS Services do not fail over when the

monitor probe is DOWN. Administrative intervention is required to fail

over the Virtual NFS Services.

AUTORECOVER. This is the default. The Virtual NFS Services fail over

when a monitor probe fails. When the NFS service is recovered on the

original node, failback occurs according to the failback policy for the

Virtual NFS Services.

NOAUTORECOVER. The Virtual NFS Services fail 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 failback policy for the Virtual NFS Services.

The

NOAUTORECOVER option is useful when integrating MxFS with a

custom application where certain application-specific actions must be

taken before failback can occur.

To set the Probe Severity from the command line, use this option:

--probeSeverity nofailover|autorecover|noautorecover