Suspending the Mirror Replication Agent instance stops replication immediately:
The Log Reader component stops scanning the transaction log immediately, and the Log Transfer Interface component stops sending LTL commands to the Replication Server immediately.
All data in the internal queues (input and output queues of the Log Reader and Log Transfer Interface components) is flushed without further processing.
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 suspend a Mirror Replication Agent instance
Log in to the Mirror Replication Agent instance with the administrator login.
Use the following command to suspend the Mirror Replication Agent:
suspend
After you invoke suspend, 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
