Quiescing the Mirror Replication Agent

Quiescing the Mirror Replication Agent instance stops replication gracefully:

The Log Reader component stops reading operations from the mirror log devices when the current scan is complete. It continues to send change-set data to the Log Transfer Interface component until it finishes processing the last operation scanned from the log.
The Log Transfer Interface component stops sending LTL commands to the Replication Server as soon as it finishes processing the last change set it receives from the Log Reader.
When the Log Transfer Interface component is finished processing its input queue and sending the resulting LTL, the Mirror Replication Agent instance releases all of its connections to the primary database (if any are open), and drops its connection to the Replication Server (and RSSD, if connected).
The Mirror Replication Agent instance goes from Replicating state to Admin state.

To quiesce a Mirror Replication Agent instance

Log in to the Mirror Replication Agent instance with the administrator login.
Use the following command to quiesce the Mirror Replication Agent:
```
quiesce
```
After you invoke the quiesce command, the Mirror Replication Agent instance should go from Replicating state to Admin state.
Use the following command to verify that the Mirror Replication Agent instance is in Admin state:
```
ra_status
```

If the internal queues are full when you invoke the quiesce command, the quiesce processing may take a while to complete, and there may be a delay before the Mirror Replication Agent instance completes its transition to Admin state.