Stay organized with collections
Save and categorize content based on your preferences.
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 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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Stop or resume a replication\n\nThis page provides instructions for how to stop or resume a replication.\n\nStop a replication\n------------------\n\nWhen you stop a replication, scheduled replication updates from the source\nvolume to the destination volume pause. The destination volume transitions from\nread-only to read-write. Both volumes continue to share the latest replication\nsnapshot as a new baseline for later resynchronization.\n\nAlthough the replication relationship between source and destination volume\ncontinues to exist, transfers are paused and the volumes become independent.\nTo re-enable the transfer of changes from source volume to destination volume,\n[resume the replication](/netapp/volumes/docs/protect-data/stop-or-resume-replication#resume_replication).\n\nUse the following instructions to stop a replication using either the\nGoogle Cloud console or Google Cloud CLI: \n\n### Console\n\n1. Go to the **NetApp Volumes page** in the Google Cloud console.\n\n[Go to NetApp Volumes](https://console.cloud.google.com/netapp/volumes)\n\n1. Click **Volumes**.\n\n2. Click the source volume. the **Details page** for the volume opens.\n\n3. Select the **Replication tab**.\n\n4. Click **Stop**. Depending on the replication transfer status, either\n stop or force stop:\n\n - **Mirrored transfer state** : Enter the source volume name and click\n **Stop**.\n\n - **Transferring** and **Preparing transfer states** : Enter the source\n volume name and click **Force stop**. A forced stop is required to stop\n a replication if a transfer is in progress at that time. Therefore, if\n you resume the replication later, recent changes may need to be\n transferred again.\n\n The replication status of the volume changes to **Stopped**. The\n destination volume becomes writable.\n\n### gcloud\n\nStop a replication: \n\n```bash\ngcloud netapp volumes replications stop REPLICATION_NAME \\\n --project=PROJECT_ID \\\n --location=LOCATION \\\n --volume=VOLUME\n```\n\nReplace the following information:\n\n- \u003cvar translate=\"no\"\u003eREPLICATION_NAME\u003c/var\u003e: the name of the replication\n you want to stop.\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the name of the project your volume\n is in.\n\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the location of the source or\n destination volume.\n\n- \u003cvar translate=\"no\"\u003eVOLUME\u003c/var\u003e: the name of the source or destination\n volume.\n\nFor more options, see\n[Google Cloud SDK documentation on volume replication](/sdk/gcloud/reference/netapp/volumes/replications).\n\nResume a replication\n--------------------\n\nYou can resume a stopped replication. When you resume a replication, all the\nchanges to the destination volume are undone and NetApp Volumes\nre-enables the replication. The destination volume transitions from read-write\nto read-only, and receives updates from the source volume at the scheduled\nreplication interval again. When you resume a replication relationship, the\ndestination volume reverts back to the latest initial replication snapshot, at\nwhich point, the volume replication process starts over.\n\nResuming a replication relationship\n-----------------------------------\n\nWhen you resume a replication relationship, any changes to the destination\nvolume while the replication was stopped are deleted.\n\nStopping a replication relationship after initialization\n--------------------------------------------------------\n\nWhen you stop a replication relationship after you initialized it, you can\nreverse the direction of the replication by swapping the source and destination\nvolume roles. Any data changes on the destination volume are lost when you\nresume the replication because the destination volume loses all changes and\nbecomes a replica of the source volume.\n\nResume a stopped replication\n----------------------------\n\nUse the following instructions to resume a stopped replication using either\nthe Google Cloud console or Google Cloud CLI. \n\n### Console\n\n1. Go to the **NetApp Volumes page** in the Google Cloud console.\n\n[Go to NetApp Volumes](https://console.cloud.google.com/netapp/volumes)\n\n1. Click **Volumes**.\n\n2. Click the name of the source volume. The **Details page** for the volume\n opens.\n\n3. Select the **Replication tab**.\n\n4. Click **Resume**.\n\n5. In the Resume volume replication dialog, review the warning.\n\n6. To resume, enter the destination volume name and click **Resume**.\n\n The replication status of the volume changes to **Mirrored**.\n\n### gcloud\n\nResume a volume replication: \n\n```bash\n gcloud netapp volumes create replications resume REPLICATION_NAME \\\n --project=PROJECT_ID \\\n --location=LOCATION \\\n --volume=VOLUME\n```\n\nReplace the following information:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the name of the project your\n volume is in.\n\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the location of the source\n or destination volume.\n\n- \u003cvar translate=\"no\"\u003eVOLUME\u003c/var\u003e: the name of source or destination\n volume.\n\nFor more options, see\n[Google Cloud SDK documentation on volume replication](/sdk/gcloud/reference/netapp/volumes/replications).\n\nWhat's next\n-----------\n\n[Reverse and resume a replication](/netapp/volumes/docs/protect-data/reverse-and-resume-replication)"]]
