Suspend-Scenario - Suspend Updates on a Replica
The Suspend-Scenario command enables you to temporarily cease delivering changes to a suspended Replica. During the suspension, changes are accumulated in a spool until replication is resumed so that re-synchronization is not required.
Important! It is imperative that during suspension, you do nothing on the Replica that causes the data to change in any way, including starting an application such as Exchange Server, SQL Server, or Oracle. If you need to start programs that will change data on the Replica, you may use the Assured Recovery option.
Notes:
- You cannot suspend replication during synchronization. You can suspend replication only temporarily, since changes are accumulated in the spool directory of the Master or upstream Replica. Make sure that sufficient disk space is available for the spool to hold the changes during the time the Replica is suspended.
- To end the suspension, use the Resume-Scenario command.
Syntax
Suspend-Scenario [-Name] <String> [-Host] <String>
Parameters
Name
The scenario name.
Host
The Replica host that you want to suspend.
Example: Suspend updates on a Replica
suspend-scenario "File Server 1" 192.168.1.153
Outcome:
Scenario File Server 1 Suspended on 192.168.1.153