HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)

Chapter 5: Configure Servers 46
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 185 for more information.)
The Server Severity can be configured on each server. The settings are:
AUTORECOVER. This is the default value for Server Severity. When the
original server is restored, HP Clustered File System 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, HP Clustered File System disables the server.
(You will need to re-enable the server with the HP CFS Management
Console or mx utility).
The
NOAUTORECOVER setting can be useful when integrating HP
Clustered File System 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.
To update a server from the command line, use this command:
mx server update [--serverSeverity=autorecover|
noautorecover] <server> ...
Other Server Configuration Procedures
Delete a Server
When a server is deleted, it is removed from the cluster and from all HP
Clustered File System applications. Applications hosted by the server
may be adversely affected by the server's removal, and any applications
that exclusively use the server will be destroyed. Before deleting a server,
be sure to take the appropriate actions:
• If the server is primary for a Virtual SQL Server, rehost the Virtual
SQL Server to another node. Also ensure that the server is not a
backup for any Virtual SQL Servers.