From 0c5d0f056881b56945b4d664f9c81954784f2251 Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Thu, 9 Jul 2026 13:24:47 -0400 Subject: [PATCH 1/2] Update pod-migration.mdx --- pods/troubleshooting/pod-migration.mdx | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/pods/troubleshooting/pod-migration.mdx b/pods/troubleshooting/pod-migration.mdx index ae0d202b..6d11a2b4 100644 --- a/pods/troubleshooting/pod-migration.mdx +++ b/pods/troubleshooting/pod-migration.mdx @@ -31,7 +31,30 @@ When prompted to migrate your Pod, you have three options: 2. **Start Pod with CPUs**: If you don't need GPU access immediately, you can start your Pod with CPUs only. This lets you access your data and manually migrate files if needed, but the Pod will have limited CPU resources and is not suitable for compute-intensive tasks. -3. **Automatically migrate Pod data**: This option spins up a new Pod with the same specifications as your current one and automatically migrates your data to a machine with available GPUs. The migration process finds a new machine with your requested GPU type, provisions the instance, and transfers your network volume data from the old Pod to the new one. +3. **Automatically migrate Pod data**: This option spins up a new Pod with the same specifications as your current one and automatically migrates your data to a machine with available GPUs. The migration process finds a new machine with your requested GPU type, provisions the instance, and transfers your network volume data from the old Pod to the new one. See [what happens during automatic migration](#what-happens-during-automatic-migration) below. + + +## What happens during automatic migration + +When you trigger an automatic Pod migration: + +1. Runpod provisions a new target Pod with the same GPU specifications as your original. The target Pod may temporarily show 0 GPUs in your pod list until the migration completes — this is expected. +2. A temporary **CPU mover pod** is deployed to handle the data transfer. This pod appears in your pod list during the migration with a billing-exempt status — you are not charged for it. Once the migration completes, it is removed automatically. +3. Your data is transferred from the old Pod to the new one. +4. The migration completes and the new Pod becomes available. +You'll receive an **email and inbox notification** when the migration starts, including the reason for migration and your source and target Pod IDs. You'll receive another notification when the migration is complete. + + +If you see an unfamiliar pod appear in your pod list during this process, it is the CPU mover pod. It will disappear once the migration is complete and you will not be charged for it. + +If a migration stalls — for example, because the source host went offline — Runpod will automatically mark it as failed after a timeout. You'll be able to initiate a new migration once the failed migration is resolved. + +## During an active migration + +While a migration is in progress, the following restrictions apply: + +- **You cannot stop or terminate the source Pod.** If you attempt to do so, you'll see the error: *"This pod has a migration in progress. Cancel the migration before terminating."* +- To stop or terminate the Pod, you must first cancel the migration from the Pod's options menu. ## Important considerations for migration From d1b33f19f5d1a9b190b4c18b43d5b166083150d9 Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Thu, 9 Jul 2026 14:30:45 -0400 Subject: [PATCH 2/2] Update pod-migration.mdx --- pods/troubleshooting/pod-migration.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/pods/troubleshooting/pod-migration.mdx b/pods/troubleshooting/pod-migration.mdx index 6d11a2b4..a973c1d9 100644 --- a/pods/troubleshooting/pod-migration.mdx +++ b/pods/troubleshooting/pod-migration.mdx @@ -47,7 +47,8 @@ You'll receive an **email and inbox notification** when the migration starts, in If you see an unfamiliar pod appear in your pod list during this process, it is the CPU mover pod. It will disappear once the migration is complete and you will not be charged for it. -If a migration stalls — for example, because the source host went offline — Runpod will automatically mark it as failed after a timeout. You'll be able to initiate a new migration once the failed migration is resolved. + +If a migration stalls because the source host went offline or becomes unreachable, Runpod will automatically mark it as failed after a timeout. You'll be able to initiate a new migration once the failed migration is resolved. ## During an active migration