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.
Stop the synchronization between the two companion servers:
sp_companion MONEY1, suspend
Stop the TruCluster resource:
/usr/sbin/caa_stop MONEY1
