3.4.0 Matrix Server Administration Guide

Chapter 3: Configure Servers 36

When the original server is restored to normal operation (for example, the

power is restored and the server is rebooted), ClusterPulse uses the

Server Severity to determine whether it is possible to fail back virtual

hosts to that server automatically. ClusterPulse also considers each virtual

host’s failback policy, which specifies whether it should fail back or

remain on the backup server. (See “Virtual Hosts and Failover” on

page 128 for more information.)

The Server Severity can be configured on each server. There are two

settings:

AUTORECOVER. This is the default value for Server Severity. When the

original server is restored, Matrix Server can automatically fail back

virtual hosts to that server, depending on the virtual host’s failback policy.

NOAUTORECOVER. After the server recovers, it is not made available to

host virtual hosts. Instead, Matrix Server disables the server. (You will

need to re-enable the server with the PolyServe Management Console or

mx utility).

The

NOAUTORECOVER setting can be useful when integrating Matrix

Server with custom applications, where additional actions may be

necessary after server recovery and before the server is made available to

host services provided by virtual hosts.

After adding a new server, it appears on the Servers window. In the

following example, two servers have been added to a matrix.

NOTE: For improved performance, the PolyServe Management Console

caches hostname lookups. If your DNS changes, you may need to

restart the console so that it will reflect the new hostname.

To add or update a server from the command line, use this command:

mx server add|update [--serverSeverity=autorecover|

noautorecover] <server> ...