If you must shut down the primary companion for maintenance but do not want to fail over to the secondary companion, you must temporarily suspend companion mode. When the companion mode is suspended, synchronization between companions does not occur, and the primary companion cannot fail over to the secondary companion. However, suspended mode is useful for performing such maintenance tasks as changing configuration parameters.
To move to suspended mode, issue:
sp_companion <primary_server_name>, suspend
Kill the monitoring process so it does not trigger a fail over when the companion server goes down. As “root”, enter:
ps -ef|grep "RUNHA_<server_name>.sh monitor" kill -9 <pid>
Shut down the primary companion.
After killing the monitoring process, you can bring the companion server down as many times as necessary and it does not fail over.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
