During a fail back, if prepare_failback executed successfully on the secondary companion but the primary companion does not start, perform the following to roll back and then reissue the prepare_failback command:
Check the primary companion’s error log, the HP MC/ServiceGuard package log, or the system log to find the reason the server failed to start, and correct the problems.
If the package for the primary companion is running on the primary node, halt the package.
Log in to the secondary companion and issue:
dbcc ha_admin ("", "rollback_failback")
dbcc ha_admin ("", "rollback_failover")
Verify that the secondary companion is in normal companion mode.
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
The secondary companion is now in failover mode. Once you verify that everything is ready for the primary companion to fail back to normal companion mode, issue sp_companion...prepare_failback.
