Troubleshooting failover  Location of error logs

Chapter 11: Active-Active Configuration for Sun Cluster 2.2

Recovering from a failed prepare_failback

During fail back, if prepare_failback executes successfully on the secondary companion but the primary companion fails to start, perform the following to roll back and then reissue the prepare_failback command:

  1. Check the primary companion’s error log and the HADBMS error log to find the reason the server failed to start, and correct the problems.

  2. Issue the following to stop monitoring the primary companion:

    hasybase stop primary_companion_name
    
  3. As “root”, issue the following to move the primary logical host back to the secondary node:

    haswitch seconary_host_name primary_log_host
    
  4. Log in to the secondary companion and issue:

    dbcc ha_admin ("", "rollback_failback")
    dbcc ha_admin ("", "rollback_failover")
    

    The companion servers should now have returned to the failover mode. For more information about dbcc ha_admin, see “dbcc options for high availability systems”.

  5. Reissue sp_companion...prepare_failback on the secondary companion.





Copyright © 2005. Sybase Inc. All rights reserved. Location of error logs

View this book as PDF