[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# Manage your volume migrations\n\nThis page describes how to manage your volume migrations.\n\nView volume migration details\n-----------------------------\n\nAfter you create a volume migration and successfully authenticate it, the\nreplication process starts.\n\nA migration's current phase is indicated by its *mirrorState*:\n\n- **Preparing**: the baseline transfer is in progress.\n\n- **Transferring**: an incremental transfer is in progress.\n\n- **Mirrored**: the migration is idle, waiting for the next hourly incremental\n transfer to start.\n\n- **Stopped**: the user stopped the migration.\n\nUse the following instructions to view details of a volume migration using 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)\n2. Under **Data protection** , click **Migrations**.\n\n3. From the list of migrations, select the migration you want to view.\n\n### gcloud\n\nTo view details of a volume migration: \n\n```\ngcloud netapp volumes replications list --volume=DESTINATION_VOLUME --location=REGION\n```\n\nEdit a volume migration\n-----------------------\n\nThe following parameters of a volume migration can be edited:\n\n- Cluster-location\n- Description\n- Labels\n\nYou can also edit the details of the destination volume using [Edit a volume](/netapp/volumes/docs/configure-and-use/volumes/manage-volume#edit_a_volume).\n\nUse the following instructions to edit details of a volume migration using the\nGoogle Cloud console: \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)\n2. Click **Volumes**.\n\n3. Click the name of the destination volume to open its details page.\n\n4. Click the **Migration** tab.\n\n5. Click **Edit migration**.\n\nStop or pause a volume migration\n--------------------------------\n\nWhen you stop a migration, the destination volume becomes read-writeable and can\nbe modified. No incremental transfers occur when the replication is stopped, but\na stopped replication can be resumed again.\n\nTo stop an active data transfer during baseline migration or if an ongoing\nincremental transfer is blocked, you must perform a forced stop. A forced stop\ninstructs the migration to save a checkpoint. This checkpoint can be used later\nby the resume operation to continue where it left off.\n\nUse the following instructions to stop or pause a volume migration using 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)\n2. Under **Data protection** , click **Migrations**.\n\n3. From the list of migrations, select the migration you want to stop.\n\n4. Click **Stop**.\n\n5. A confirmation dialog with information is displayed. Enter the volume name\n and click **Stop** to confirm.\n\n6. If a transfer is running, another dialog is displayed asking if you want to\n perform a force stop. A force stop cancels the current transfer and reverts\n the destination volume back to the last successful transfer. You can either\n cancel the dialog and wait for the transfer to complete or initiate a force\n stop.\n\n7. Wait for the **Transfer status** to change to **Stopped**.\n\n### gcloud\n\nTo stop or pause a volume migration: \n\n```\ngcloud netapp volumes replications stop REPLICATION_NAME \\\n --volume=DESTINATION_VOLUME --location=REGION\n```\n\nIf the command returns an error due to baseline or incremental transfer that\nis in progress, you can add the `--force` flag to the command to force a stop\nand create a checkpoint for a later resume operation.\n\nResume a volume migration\n-------------------------\n\nWhen you resume a migration, the destination volume reverts to the latest\ncommon checkpoint or snapshot with the source volume. Incremental transfers then\nstart from this point. This action undoes any changes made to the destination\nvolume's content, so make sure this is your required outcome. Destination volume\nsettings such as size, protocol settings, and policies won't be synchronized\nwith the source volume.\n\nUse the following instructions to resume a volume migration using 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)\n2. Under **Data protection** , click **Migrations**.\n\n3. From the list of migrations, select the migration you want to resume.\n\n4. Click **Resume**.\n\n5. A confirmation dialog with information is displayed. Enter the volume name\n and click **Resume** to confirm.\n\n6. Wait for the **Transfer status** to change to **Preparing** or **Mirrored**.\n\n### gcloud\n\nTo resume a volume migration: \n\n```\ngcloud netapp volumes replications resume REPLICATION_NAME \\\n --volume=DESTINATION_VOLUME --location=REGION\n```\n\nSync a volume migration\n-----------------------\n\nThe sync operation lets you run a manual, unscheduled incremental transfer on a\nmigration that is in a mirrored transfer state. This operation is used during\ncutover to transfer the latest changes from the source to the destination\nimmediately, without waiting for the next scheduled incremental transfer.\n\nThe service lets you run up to a maximum of five sync operations per volume per\nday.\n\nUse the following instructions to sync a volume migration using 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)\n2. Under **Data protection** , click **Migrations**.\n\n3. From the list of migrations, select the migration you want to sync.\n\n4. Click **Sync now**.\n\n5. A confirmation dialog with information is displayed. Enter the volume name\n and click **Sync now** to confirm.\n\n6. Wait for the operation to finish.\n\n### gcloud\n\nTo sync a volume migration: \n\n```\ngcloud netapp volumes replications sync REPLICATION_NAME \\\n --volume=DESTINATION_VOLUME --location=REGION\n```\n\nCutover a volume migration\n--------------------------\n\nTo perform a [cutover](/netapp/volumes/docs/migrate/ontap/overview#cutover),\ncomplete the following steps:\n\n1. Make sure all settings on the destination volume are correct. For more\n information about protocol options, export, and snapshot policies, see\n [Volume details](/netapp/volumes/docs/configure-and-use/volumes/manage-volume#edit_a_volume).\n\n2. Wait for an ongoing incremental transfer to finish. This is confirmed when\n the mirrorState shows as **Mirrored** in the [Volume migration details](/netapp/volumes/docs/migrate/ontap/manage-volume-migration#view_volume_migration_details) page.\n\n3. Stop all write access to the source volume. This can be done by shutting down\n the applications or removing access permissions for clients.\n\n4. Run a [sync operation](#sync_a_volume_migration) to transfer the latest\n changes from the source to the destination. The *mirrorState* will change to\n **Transferring** and back to **Mirrored** after the transfer is complete.\n\n5. [Stop the migration](#stop_or_pause_a_volume_migration) to make the\n destination volume read-writeable.\n\n6. Restart clients and applications, this time using the destination volume.\n\n7. Optional: consider [setting up backups](/netapp/volumes/docs/protect-data/set-up-volume-backups)\n for the destination volume.\n\n8. Finally, [cleanup the volume migration](#delete_a_volume_migration) by\n deleting it.\n\nDelete a volume migration\n-------------------------\n\nYou can delete a volume migration after the migration is complete and you have\neither cutover your workload or decided to cancel the migration.\n\nThe volume migration deletion includes the following cleanup steps:\n\n1. Make sure the migration status is **Stopped**.\n\n2. Delete the replication.\n\n3. Consider deleting the cluster peering to NetApp Volumes on\n your source ONTAP cluster using the `cluster peer delete` command, but only\n if this was the last migration from your source ONTAP cluster.\n\n | **Caution:** Don't delete cluster peering if other migrations to the same NetApp Volumes cluster are still in progress.\n4. Remove any additional networking set up for the migration once it's\n completed.\n\n| **Note:** If the baseline transfer for your destination volume isn't completed, deleting the replication also deletes the destination volume to prevent it from being left in an *inactive* state. However, if the baseline transfer has finished, deleting the replication doesn't delete the destination volume.\n\nUse the following instructions to delete a stopped volume migration using 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)\n2. Under **Data protection** , click **Migrations**.\n\n3. From the list of migrations, select the migration you want to delete.\n\n4. Click **Finish migration**. This action deletes the migration.\n\n5. A confirmation dialog with information is displayed. Enter the migration\n name and click **Finish** to confirm.\n\n### gcloud\n\nTo delete a stopped volume migration: \n\n```\ngcloud netapp volumes replications delete REPLICATION_NAME \\\n --volume=DESTINATION_VOLUME --location=REGION\n```\n\nWhat's next\n-----------\n\n[Change volume settings during volume migration](/netapp/volumes/docs/migrate/ontap/change-volume-settings-volume-migration)."]]