When a Replication Agent instance is operating normally and replicating data, it is in the Replicating state.
In the Replicating state, the Replication Agent instance is connected to the primary database and the primary Replication Server, and it is scanning its transaction log for transactions to be replicated. Actual replication (sending LTL output) does not have to be taking place for the Replication Agent instance to be in the Replicating state.
To go from the Replicating state to the Admin state, you can invoke either the suspend or quiesce command.
The suspend command immediately stops all Replication Agent processing, shuts down connections to the primary database and the primary Replication Server, and puts the Replication Agent instance in the Admin state.
The quiesce command stops all Log Reader processing of new data in the transaction log, finishes processing any change set data in the Replication Agent internal queues, shuts down connections to the primary database and the primary Replication Server, and then puts the Replication Agent instance in the Admin state.
