Failback switches the service group that originally belonged to the primary node from the secondary node back to the primary node and brings it online. Before initiating failback, clear the failed-over Sybase resource:
hares -clear failed_over_Sybase_resource_name
To initiate failback:
Issue the following from the secondary companion, after your primary node is ready to take back the service group:
sp_companion primary_companion_name, prepare_failback
where primary_companion_name is the name of primary companion. This command switches the primary node's service group from the secondary node back to the primary node. For example, to fail back the primary companion MONEY1, issue this command from the secondary companion PERSONEL1:
sp_companion "MONEY1", prepare_failback
Step: Primary databases are shutdown in secondary. Step: Primary databases dropped from current secondary. Step: Primary devices released from current secondary. Step: Prepare failback for primary server completed successfully.
Make sure the primary node’s service group is successfully switched to primary node by issuing this command from the command line:
hastatus -group service_group_name
This command displays the status of the primary node's service group. All resources except the Sybase resource should be online. Issue the following to bring the Sybase resource online:
hares -online failedback_Sybase_resource_name -sys primary_node_name
Issue the following from the primary companion, to resume normal companion mode:
sp_companion secondary_companion_name, resume
where secondary_companion_name is the name of the secondary companion server. For example, to resume normal companion mode for primary companion MONEY1:
sp_companion "PERSONEL1", resume
You cannot connect clients with the failover property to Adaptive Server until you issue sp_companion resume. If you attempt to reconnect them after issuing sp_companion prepare_failback, the client hangs until you issue sp_companion resume.