This page provides instructions for how to stop or resume a replication.
Stop a replication
When you stop a replication, scheduled replication updates from the source volume to the destination volume pause. The destination volume transitions from read-only to read-write. Both volumes continue to share the latest replication snapshot as a new baseline for later resynchronization.
Although the replication relationship between source and destination volume continues to exist, transfers are paused and the volumes become independent. To re-enable the transfer of changes from source volume to destination volume, resume the replication.
Use the following instructions to stop a replication using either the Google Cloud console or Google Cloud CLI:
Console
- Go to the NetApp Volumes page in the Google Cloud console.
Click Volumes.
Click the source volume. the Details page for the volume opens.
Select the Replication tab.
Click Stop. Depending on the replication transfer status, either stop or force stop:
Mirrored transfer state: Enter the source volume name and click Stop.
Transferring and Preparing transfer states: Enter the source volume name and click Force stop. A forced stop is required to stop a replication if a transfer is in progress at that time. Therefore, if you resume the replication later, recent changes may need to be transferred again.
The replication status of the volume changes to Stopped. The destination volume becomes writable.
gcloud
Stop a replication:
gcloud netapp volumes replications stop REPLICATION_NAME \ --project=PROJECT_ID \ --location=LOCATION \ --volume=VOLUME
Replace the following information:
REPLICATION_NAME: the name of the replication you want to stop.PROJECT_ID: the name of the project your volume is in.LOCATION: the location of the source or destination volume.VOLUME: the name of the source or destination volume.
For more options, see Google Cloud SDK documentation on volume replication.
Resume a replication
You can resume a stopped replication. When you resume a replication, all the changes to the destination volume are undone and NetApp Volumes re-enables the replication. The destination volume transitions from read-write to read-only, and receives updates from the source volume at the scheduled replication interval again. When you resume a replication relationship, the destination volume reverts back to the latest initial replication snapshot, at which point, the volume replication process starts over.
Resuming a replication relationship
When you resume a replication relationship, any changes to the destination volume while the replication was stopped are deleted.
Stopping a replication relationship after initialization
When you stop a replication relationship after you initialized it, you can reverse the direction of the replication by swapping the source and destination volume roles. Any data changes on the destination volume are lost when you resume the replication because the destination volume loses all changes and becomes a replica of the source volume.
Resume a stopped replication
Use the following instructions to resume a stopped replication using either the Google Cloud console or Google Cloud CLI.
Console
- Go to the NetApp Volumes page in the Google Cloud console.
Click Volumes.
Click the name of the source volume. The Details page for the volume opens.
Select the Replication tab.
Click Resume.
In the Resume volume replication dialog, review the warning.
To resume, enter the destination volume name and click Resume.
The replication status of the volume changes to Mirrored.
gcloud
Resume a volume replication:
gcloud netapp volumes create replications resume REPLICATION_NAME \ --project=PROJECT_ID \ --location=LOCATION \ --volume=VOLUME
Replace the following information:
PROJECT_ID: the name of the project your volume is in.LOCATION: the location of the source or destination volume.VOLUME: the name of source or destination volume.
For more options, see Google Cloud SDK documentation on volume replication.
What's next
Reverse and resume a replication