Pausing and resuming replication or recovery of a tenant
You can pause and resume replication or recovery of an individual tenant on a replication link. Pausing replication or recovery of a tenant on a link causes the Replication service on the sending system to stop all send activity for the tenant on that link. With an active/active link, the Replication service on both systems involved in the link stops all send activity for the tenant on the link.
Resuming replication or recovery of a tenant on a link restarts all send activity for that tenant on that link. After pausing replication or recovery of a tenant on a link, you need to resume replication or recovery manually.
You might pause replication of some tenants on a link, for example, to give more processing time to other tenants with greater replication backlogs. While replication or recovery of a tenant is paused on a link, the two systems involved in the link can still use the link to read from each other the objects in the tenant's replicated namespaces.
Replication or recovery of a tenant can also be paused automatically due to certain events. After replication or recovery of a tenant is paused automatically, you need to resume replication or recovery manually. However, you cannot do this until the issue that caused replication or recovery to be paused is resolved.
Pausing replication or recovery of a tenant on a link in an erasure coding topology prevents each system involved in the link from sending full copies of object data and chunks for objects in the tenant's namespaces to the other system over that link. Pausing replication or recovery of a tenant, therefore, may prevent newly ingested objects in those namespaces from being protected.
Pausing replication or recovery of a tenant on a link does not prevent full copies of object data in the tenant's namespaces from being reduced to chunks on the systems involved in that link.
The Replication service periodically checkpoints its progress. When you pause replication or recovery of a tenant, no special checkpoint occurs. When you resume processing, therefore, processing starts from the last checkpoint before the pause.