During a failback, if prepare_failback was executed successfully on the secondary companion but the primary companion does not boot:
Check the cluster system error logs and Adaptive Server logs to find the reason the failback failed and correct any problem(s).
Clear any “faulted” states in the resources of the service group.
hares -clear resource_name
If the service group has been moved from the secondary host to the primary host, switch it back to the secondary host:
hagrp -switch sybase_group_name -to secondary_host
Log in to the secondary companion and issue:
dbcc ha_admin ("", "rollback_failback")
Your companion servers should both be back in failover mode. For more information about dbcc ha_admin, see “dbcc Options for High Availability Systems”.
Reissue sp_companion...prepare_failback on the secondary companion.
