You can use Sybase Central or the procedure discussed in this section to quiesce a system consisting of several Replication Servers.
To quiesce a replication system:
Execute the suspend log transfer from all command at each Replication Server. This prevents RepAgent from connecting to the Replication Servers.
Execute admin quiesce_force_rsi at each Replication Server.
This command forces Replication Server to deliver all queued messages to other Replication Servers, then reports whether the system is successfully quiesced.
Quiescing occurs most efficiently if you follow the flow of the data. For example, if data flows from TOKYO_RS to MANILA_RS to SYDNEY_RS, quiesce the Replication Servers in that order.
Check that the Replication Server is quiescent using admin quiesce_check. If necessary, repeat steps 2 and 3 until all Replication Servers are quiescent.
After all Replication Servers are quiescent, execute admin quiesce_force_rsi once more at each Replication Server. Check that each Replication Server is quiescent using admin quiesce_check. If necessary, repeat this step until all Replication Servers are quiescent.
This step is necessary because, although a Replication Server may be quiescent, it may have recently sent messages to another Replication Server. These messages may initiate more communication between these two Replication Servers or between several Replication Servers in the replication system. Repeating steps 2 and 3 ensures that you have quiesced the entire replication system.
