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 system event log to find the reason the server failed to boot, and correct the problems.
Check that the MSCS group that contains the resource for the primary server is located on the secondary node. If not, use Move Group to move it there
Login to the secondary companion and issue:
dbcc ha_admin ("", "rollback_failback")
dbcc ha_admin ("", "rollback_failover")
Verify secondary companion is in normal companion mode
Check that the MSCS resource for the primary server is online. If not, manually bring the resource online using the Cluster Administrator.
As root, start up the package for the primary companion to run on secondary node.
/usr/sbin/cmrunpkg -n <secondary_node> primary_companion_package_name
Your secondary companion is now in failover mode. Once you verify that everything is ready for the primary companion to failback to normal companion mode, you can either issue sp_companion...prepare_failback or Move Group.
