3.4.0 MxFS for CIFS Administration Guide
Chapter 3: Configure CIFS with Virtual CIFS Servers 22
Copyright © 1999-2006 PolyServe, Inc. All rights reserved.
You can specify a new application name, select an existing application
name, or leave this field blank. However, if you do not assign a name,
Matrix Server will use the IP address of the Virtual CIFS Server as the
application name.
Policy: The policy determines the failback action that the Virtual CIFS
Server will take following a failover to a backup node.
•
AUTOFAILBACK. This policy is intended to return the Virtual CIFS
Server to its original configuration, or as close to it as possible. After
the Virtual CIFS Server fails over to a backup node, the ClusterPulse
process watches the health of the nodes that are higher in the list of
servers configured for that Virtual CIFS Server. When the health of
one of these nodes is equal to or greater than the backup node where the
Virtual CIFS Server currently resides, the Virtual CIFS Server will
automatically attempt to fail over to that node.
•
NOFAILBACK. This policy is intended to minimize failovers and is the
default. The Virtual CIFS Server remains active on the backup node
until a “healthier” node becomes available, at which point the Virtual
CIFS Server fails over to that node. (On a “healthier” node, more of
the services associated with the Virtual CIFS Server will be up than on
the node currently hosting the Virtual CIFS Server.)
Network Interfaces Available/Members: Move the interfaces on which
the Virtual CIFS Server should be configured from the Network Interfaces
Available column to the Members column. The first interface that you
select is the primary interface. The other interfaces that you select are
backups. You can use the up and down arrows to reorder the interfaces
on the Members column.
When you click OK, the Virtual CIFS Server appears on the Servers,
Virtual Hosts, and Applications tabs on the PolyServe Management
Console. The following example of the Servers view shows a Virtual CIFS
Server configured on two nodes; one node is the primary and the other is
a backup.