During failback, if prepare_failback is successfully executed on the secondary companion but the primary companion fails to boot. Roll back and then reissue the prepare_failback command:
Check the cluster system error logs, callback error logs, high availability agent fault monitor error logs, and Adaptive Server error logs to find the reason the failback failed, and correct any problems.
Clear any error states in the resources of the resource group. To determine the states of resources and resource groups enter:
scha_resourcegroup_get -o RG_STATE -a resource_group_name scha_resource_get -o RESOURCE_STATE_NODE -R resource_name node_name
Issue the following command to clear the STOP_FAILED state:
scswitch -c -h node_name -j resource_name -f STOP_FAILED
Log in to the secondary companion and issue:
dbcc ha_admin("", "rollback_failback")
To fail back, repeat these steps.
