Stay organized with collections
Save and categorize content based on your preferences.
This page provides details about how to reverse and resume a replication.
About the reverse and resume operation
When you reverse and resume a replication, it switches the source and destination
roles of your volumes; the destination volume becomes the new source volume and
the source volume becomes the new destination volume. This operation is
immediately followed by a resume operation, which overwrites the contents of the
new destination volume with the contents of the new source volume. If you
reverse and resume a replication twice, the original replication direction
re-establishes.
Reverse and resume operation use case
After you stop replication and make changes to the destination volume, you can
replicate those changes back to the source volume. This process is common in a
disaster recovery scenario in which you operate on the destination volume for a
period of time and want to switch roles of the volumes.
Considerations
Consider the following before you use reverse and resume operation:
If you use reverse and resume operations incorrectly, you might experience
unintended data loss. Make sure that you know the current and future roles of
your source and destination volumes because changes on the new destination
volume are overwritten with the new source volume.
While you can use a destination volume to take manual backups, the service
doesn't support the scheduled backups from a destination volume. Before you
reverse a volume replication, make sure to remove any backup policy from the
volume that becomes new destination volume.
If you plan to continuously operate with reversed replication direction, it's
recommended to set up a backup for the new source volume. If you intend to
revert replication back to the original source and switch directions again,
make sure to enable scheduled backups on the source volume after completion.
Reverse and resume a replication
Use the following instructions to reverse and resume a replication using
the Google Cloud console or Google Cloud CLI:
Console
Go to NetApp Volumes page in the Google Cloud console.
Click the name of the volume. The Details page for the volume
appears.
Select the Replication tab.
Ensure that the replication status is set to Stopped.
Click Reverse and resume replication.
In the Reverse volume replication and resume dialog, enter the
new destination volume that you want to overwrite to confirm
the reverse and resume action.
Click Reverse and resume to initiate the operation.
In the overview of the volume, note that the role, either source or
destination, changes and names of source and destination volume change as
well. An incremental transfer operation to update the new destination
volume triggers immediately after you initiate the reverse and resume
operation.
gcloud
Run the following command to reverse and resume a volume replication:
[[["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,["# Reverse and resume a replication\n\nThis page provides details about how to reverse and resume a replication.\n\nAbout the reverse and resume operation\n--------------------------------------\n\nWhen you reverse and resume a replication, it switches the source and destination\nroles of your volumes; the destination volume becomes the new source volume and\nthe source volume becomes the new destination volume. This operation is\nimmediately followed by a resume operation, which overwrites the contents of the\nnew destination volume with the contents of the new source volume. If you\nreverse and resume a replication twice, the original replication direction\nre-establishes.\n\nReverse and resume operation use case\n-------------------------------------\n\nAfter you stop replication and make changes to the destination volume, you can\nreplicate those changes back to the source volume. This process is common in a\ndisaster recovery scenario in which you operate on the destination volume for a\nperiod of time and want to switch roles of the volumes.\n\nConsiderations\n--------------\n\nConsider the following before you use reverse and resume operation:\n\n- If you use reverse and resume operations incorrectly, you might experience\n unintended data loss. Make sure that you know the current and future roles of\n your source and destination volumes because changes on the new destination\n volume are overwritten with the new source volume.\n\n- While you can use a destination volume to take manual backups, the service\n doesn't support the scheduled backups from a destination volume. Before you\n reverse a volume replication, make sure to remove any backup policy from the\n volume that becomes new destination volume.\n\n- If you plan to continuously operate with reversed replication direction, it's\n recommended to set up a backup for the new source volume. If you intend to\n revert replication back to the original source and switch directions again,\n make sure to enable scheduled backups on the source volume after completion.\n\nReverse and resume a replication\n--------------------------------\n\nUse the following instructions to reverse and resume a replication using\nthe Google Cloud console or Google Cloud CLI: \n\n### Console\n\n1. Go to **NetApp Volumes page** in the Google Cloud console.\n\n [Go to NetApp Volumes](https://console.cloud.google.com/netapp/volumes)\n2. Click **Volumes**.\n\n3. Click the name of the volume. The **Details page** for the volume\n appears.\n\n4. Select the **Replication tab**.\n\n5. Ensure that the replication status is set to **Stopped**.\n\n6. Click **Reverse and resume replication**.\n\n7. In the **Reverse volume replication and resume dialog** , enter the\n **new destination volume** that you want to overwrite to confirm\n the reverse and resume action.\n\n8. Click **Reverse and resume** to initiate the operation.\n\n In the overview of the volume, note that the role, either source or\n destination, changes and names of source and destination volume change as\n well. An incremental transfer operation to update the new destination\n volume triggers immediately after you initiate the reverse and resume\n operation.\n\n### gcloud\n\nRun the following command to reverse and resume a volume replication: \n\n```bash\n gcloud netapp volumes replications reverse \\\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 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 [Google Cloud SDK documentation on volume replication](/sdk/gcloud/reference/netapp/volumes/replications).\n\nWhat's next\n-----------\n\n[Integrate Active Directory](/netapp/volumes/docs/configure-and-use/active-directory/about-ad)."]]
