If
the automatic failback did not execute successfully, examine the
logs to make sure that the high availability system performed the
following steps. If it did not, perform them manually, and perform
them in the sequence described below.
Relocate the primary node’s TruCluster resource to the secondary node. This shuts down the primary companion and fails over its resources to the secondary companion.
Shut down and then restart your secondary companion.The server_name.scr restarts the companion automatically after you shut it down if RETRY is set to a value greater than 0.
Using isql log in as LOGIN_NAME to the secondary companion and verify that it is running in secondary failover mode.
Issue sp_companion 'prepare_failback'. For example, to fail back from the secondary companion PERSONNEL1:
sp_companion MONEY1, 'prepare_failback'
Relocate the TruCluster resource to the primary node.
Log in to the primary companion using isql and make sure that it is running in primary failback mode.
Issue sp_companion 'resume'. For example, to resume companion mode for primary companion MONEY1:
sp_companion PERSONNEL1, 'resume'
You cannot connect clients with the failover property
until you issue sp_companion resume.
If you attempt to reconnect them after issuing sp_companion
prepare_failback, the client stops responding
until you issue sp_companion resume.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
