During a failback, if prepare_failback was executed successfully on the secondary companion but the primary companion does not boot:
Check the primary companion’s errorlog and the cluster error log to identify why the server did not boot, and correct the problems.
To clear the FAULTED state of the HAase resource, issue:
hasybase clear HAase_res_name
As root, issue the following to move the primary logical host back to the secondary node:
hagrp -switch primary_service_group -to secondary_host_name
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.
