--- title: "Protection Domain Migration (Planned Failover)" slug: "protection-domain-migration-planned-failover" updated: 2025-08-27T14:21:15Z published: 2025-08-27T14:21:15Z canonical: "kb.expedient.com/protection-domain-migration-planned-failover" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.expedient.com/llms.txt > Use this file to discover all available pages before exploring further. # Protection Domain Migration (Planned Failover) DR at Expedient is typically configured and executed entirely through Prism Central, but in some cases, you may need to utilize Production Domains at the Prism Element level. ## Planned Failover - Migration A planned failover (Migration) is initiated from the **primary/source** side of replication. After a failover, the target site enables certain VM properties, such as CPU hotplug and Virtual SCSI, by default, if they were configured with a non-default value on the source site in the following cases: - When activating a protection domain on the target cluster. - When restoring or cloning VMs using a snapshot on the target cluster. The VMs on the target cluster do not boot if the applications or the OS running on them do not support the settings for retaining CPU hotplug and Virtual SCSI properties. > [!NOTE] > To ensure a smooth failover for VMs that have a non-default value of CPU hotplug and Virtual SCSI properties, upgrade both the source and target clusters to AOS versions that support those properties. #### Consideration - The VMs on the remote site are **not** powered on automatically. - This allows you to resolve any potential network configuration issues, such as IP address conflicts, before powering on the VMs. - You must manually reattach the volume groups that were affected by the migration or restore operation, perform in-guest iSCSI attachment. - If you use the nCLI for attaching volume groups, note that the UUIDs of volume groups change when they are restored at the remote site, and so do their iSCSI target names, which contain the volume group UUID. - For more information, see [Volume Group Configuration](https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism:wc-volume-group-configure-c.html) in the Prism Element Web Console Guide. ### Migration to a Remote Site 1. Log in to the Prism Element web console for the primary site. 2. From the dropdown menu, select **Data Protection.** 3. Go to **Table** > **Async DR.** 1. The system displays a list of protection domains configured for asynchronous data replication in the cluster. 4. Select the protection domain to migrate and click **Migrate**. 1. The system displays the **Migrate Protection Domain** dialog box. 2. Either right-click the **Protection Domain** to Migrate or click the **Migrate** option in the lower right portion of the window. ![](https://cdn.document360.io/69e9f9c7-5da8-45e7-a671-4b8287f36122/Images/Documentation/protection-domain-migration-planned-failover-image-ytl74djq.png) 1. Select the site where you want to migrate the protection domain, and type **MIGRATE** in the text box. 1. Click **Migrate** button to begin. ![](https://cdn.document360.io/69e9f9c7-5da8-45e7-a671-4b8287f36122/Images/Documentation/protection-domain-migration-planned-failover-image-6h8ilful.png) b. A task will begin, and a banner will pop up noting that the Protection Domain migration was started successfully. ![](https://cdn.document360.io/69e9f9c7-5da8-45e7-a671-4b8287f36122/Images/Documentation/protection-domain-migration-planned-failover-image-9kux31dz.png) ![](https://cdn.document360.io/69e9f9c7-5da8-45e7-a671-4b8287f36122/Images/Documentation/protection-domain-migration-planned-failover-image-j30iaslx.png) #### Migrating a protection domain does the following: - Creates and replicates a snapshot of the protection domain. - Powers off the VMs on the primary site. - Creates and replicates another snapshot of the protection domain. - Unregisters all VMs and volume groups and removes their associated files. - Marks the primary site protection domain as inactive. - Restores all VM and volume group files from the last snapshot and registers them with the same UUIDs at the remote site - Marks the remote site protection domain as active - The VMs in the Protection Domain are deleted from the primary cluster and only present on the remote/target cluster > [!NOTE] > VM Shutdown Note > > The data protection service waits for 5 minutes for the VM to shutdown. If the VM does not get shutdown within 5 minutes, it is automatically powered off. > > > > Please remember that the VMs are **NOT** automatically powered on after a failover. All of the VMs in the Protection Domain must be manually powered on. ## Migrate Back to Source Site After a failover (planned or unplanned), you will likely need to eventually migrate back to the source cluster. > [!WARNING] > When performing Protection Domain failover, reverse replication is **NOT** automatically configured back to the paired remote site. Local snapshots of the Protection Domain are taken on the ***new*** source cluster, but those snapshots are not replicated and must be set up again manually. To set up snapshot replication to the remote site, you must configure a schedule on the Protection Domain, similar to configuring a scheduling when creating the Production Domain in the first place. 1. Log in to the Prism Element GUI of the **now** primary/source cluster for the Protection Domain. 1. The ‘Active’ Protection Domain will display a **green dot** icon next to the name. ![](https://cdn.document360.io/69e9f9c7-5da8-45e7-a671-4b8287f36122/Images/Documentation/protection-domain-migration-planned-failover-image-pabe0dgg.png) 1. Right click the name of the Protection Domain and select **Update.** 2. The update Protection Domain window will open and display the protected entities in the Protection Domain. Click the Schedule tab to configure a new remote replication schedule. ![](https://cdn.document360.io/69e9f9c7-5da8-45e7-a671-4b8287f36122/Images/Documentation/protection-domain-migration-planned-failover-image-3y51s27e.png) 1. Click the **New Schedule** button and configure the required schedule to replicate snapshots to the new remote site. (The previously ‘Active’ site) 1. Configure the schedule as needed and click **Create Schedule.** 1. Data Protection will now show replication back to the remote site. ![](https://cdn.document360.io/69e9f9c7-5da8-45e7-a671-4b8287f36122/Images/Documentation/protection-domain-migration-planned-failover-image-c7p6c7rd.png)