During fail back, if prepare_failback was 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 system event log to find the reason the server does not start, 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, it does use Move Group to move it.
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.
Check that the MSCS resource for the primary server is online. If it is not, manually bring the resource online using the Cluster Administrator.
As “root,” start 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 fail back to normal companion mode, you can either issue sp_companion...prepare_failback or use the Move Group option.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
