During fail back, if prepare_failback executed successfully on the secondary companion but the primary companion fails to start, perform the following to roll back, then reissue the prepare_failback command:
Check the primary companion’s error log and the TruCluster error log to find the reason the server failed to start, and correct the problems.
Use caa_stop server_name the TruCluster service on the primary node.
Log in to the secondary companion as LOGIN_NAME, and issue:
dbcc ha_admin ("", "rollback_failback")
dbcc ha_admin ("", "rollback_failover")
This returns the companion servers to failover mode.
Restart the TruCluster resource on the primary node.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
