During a failback, if prepare_failback was executed successfully on the secondary companion but the primary companion fails to boot, perform the following to rollback and then reissue the prepare_failback command:
Check the primary companion’s error log and the TruCluster error log to find the reason the server failed to boot, and correct the problems.
Stop the TruCluster service on the primary node with caa_stop server_name
Login to the secondary companion as LOGIN_NAME, and issue:
dbcc ha_admin ("", "rollback_failback")
dbcc ha_admin ("", "rollback_failover")
Your companion servers should both be back in the failover mode
Restart the TruCluster resource on the primary node.
