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 the companions does not occur, and the primary companion cannot fail over to the secondary companion. However, suspended mode is very useful for performing such maintenance tasks as changing configuration parameters:
To move to suspended mode, issue:
sp_companion <primary_server_name>, suspend
For example, to suspend primary companion MONEY1:
sp_companion MONEY1, suspend
Kill the monitoring process so it does not trigger a failover when the companion server goes down. As “root,” enter:
ps -ef|grep "RUNHA_<server_name>.sh monitor" kill -9 <pid>
For example, to kill the monitoring process for MONEY1 which has a pid of 2509:
ps -ef|grep "RUNHA_MONEY1.sh monitor" kill -9 2509
Shut down the primary companion.
After killing the monitoring process, you can bring the companion server down as many times as necessary and it will not failover.
