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

Chapter 15: Configure Virtual Hosts 181
select an existing application name, or leave this field blank. However, if
you do not assign a name, HP Clustered File System will use the IP
address for the virtual host as the application name.
Always active: If you check this box, upon server failure, the virtual host
will move to an active server even if all associated service and device
monitors are inactive or down. If the box is not checked, failover will not
occur when all associated service and device monitors are inactive or
down and the virtual host will not be made active anywhere. (See
“Virtual Host Activeness Policy” on page 186 for details.)
Policy: The policy determines the failback action that the virtual host will
take following a failover to a backup server.
As part of configuring a virtual host, you will need to select network
interfaces located on the servers that can be used for the virtual host. The
interfaces are placed in order: primary, backup #1, backup #2, and so on.
The ClusterPulse process considers the “health” of the servers providing
those interfaces when determining where to place a virtual host. The
status and enablement of each monitor contributes to the health of a
server with respect to the virtual host. When a server is completely
“healthy,” all of the services associated with the virtual host are up and
enabled.
•
AUTOFAILBACK. This is the default policy. It 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, HP Clustered File
System watches the health of the servers higher in the list for that
virtual host. When the health of one of these servers is equal to or
greater than the backup server where the virtual host currently
resides, the virtual host will automatically attempt to fail over to that
server.
•
NOFAILBACK. This policy is intended to minimize failovers. The
virtual host remains active on the backup server until a “healthier”
server becomes available, at which point the virtual host fails over to
that server. (On a “healthier” server, more of the services associated
with the virtual host will be up than on the server currently hosting
the virtual host.)