82 Monitoring PowerVault NX3500
Clients that use NFS are stateless and are not affected during fail-back.
Clients that use connection-based protocols (CIFS), may be disconnected
during fail-back. To optimize the fail-back operation, the system provides you
with the following policies for migration on recovery, which affect the load-
balance and disconnections:
Migrate Immediately—Always keep the system well balanced, at the cost
of possibly disconnecting CIFS clients during work time.
Migrate Automatically— Always keep the system well balanced if the
controller failure is very short, at the cost of disconnecting CIFS clients.
This option causes the system to remain unbalanced for a period of several
days, if the failure remains for long time.
This mode overcomes short controller failures because clients have not
created new material during the short time failure. Therefore, the best
practice is to rebalance them as soon as possible.
If the failure is longer than 10 minutes, the system remains unbalanced
until you rebalance it manually.
Migrate Manually— Never migrates clients automatically. This requires
manual intervention to rebalance the system.
If the system requires manual intervention to rebalance it after fail-over,
the system sends an appropriate email message to the administrator.
You can configure the fail-back policy, as described above, per protocol and
LAN or client network.
CIFS Connections
The CIFS Connections page enables you to monitor current CIFS
connections. To manage CIFS connections, choose MonitorLoad
BalancingCIFS Connections. The CIFS Connection page is displayed.