Preventing automated client failover
You can configure the client to prevent automated client failover to the secondary server.
About this task
You might want to prevent automated client failover, for example, if you know that the data on the client node was not replicated to the secondary server before the primary server went offline. In this case, you do not want to recover any replicated data from the secondary server that might be old.
Procedure
To prevent the client node from failing over to the secondary server, add the following statement to the client options file:
usereplicationfailover noThis setting overrides the configuration that is provided by the Tivoli® Storage Manager server administrator on the primary server.
Results
The client node does not automatically fail over to the secondary server the next time it tries to connect to the offline primary server.