When you register the logical hosts, disable the automatic
failback option. Fail back should be a planned event.
Failback moves the primary companion’s shared disks from the secondary node back to the primary node and starts the primary companion on the primary node.
When the primary host is ready to take over the primary companion, issue this command from the secondary companion:
sp_companion primary_companion_name, prepare_failback
where primary_companion_name is the name of primary companion server.
This command moves the primary companion’s logical host to the primary host.
Make sure the primary companion’s logical host is moved successfully to the primary host by issuing this command:
haget -f mastered
The output shows the primary host monitoring the logical host of the primary companion.
Start the primary companion:
hasybase start primary_companion_name
To resume normal companion mode, issue the following from the primary companion.
sp_companion secondary_companion_name, resume
where secondary_companion_name is the name of the secondary companion server.
You cannot connect clients with the failover property
until you issue sp_companion resume.
If you do try to reconnect them after issuing sp_companion
prepare_failback, the client hangs until you
issue sp_companion resume.
Copyright © 2005. Sybase Inc. All rights reserved. |
![]() |