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 HADBMS error log to find the reason the server failed to boot, and correct the problems.
Issue the following to stop monitoring the primary companion:
hasybase stop primary_companion_name
As root, issue the following to move the primary logical host back to the secondary node:
haswitch seconary_host_name primary_log_host
Login to the secondary companion and issue:
dbcc ha_admin ("", "rollback_failback")
dbcc ha_admin ("", "rollback_failover")
Your companion servers should both be back in the 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.
