Mount and migrate a file system for instant recovery to any target
Stay organized with collections
Save and categorize content based on your preferences.
The file system mount and migrate feature is available for recovery of Linux
file systems that are backed up into a logical volume manager (LVM) based
staging disk—as LVM is used for the online migration during recovery.
If the source file system is less than 1 TiB or is not on a logical volume
manager, a flag Prefer LVM on Staging Disk needs to be set to force logical
volume manager onto the Backup and DR staging disk. Backups of file
systems that are larger than 1 TiB are automatically backed up in logical volume
manager format, regardless of whether the Prefer LVM for Single Staging Disk
option is set or not.
Known limitations
The target volume group extent size must be identical to the production volume
group at the time of backup. If the production system does not have LVM,
the staging disk uses a default extent size of 4 MB.
Use mount and migrate to restore data back to the same server location
The following must be true for images from any file system application to be
restored using the mount and migrate option:
The Application and Details setting Prefer LVM on Staging disk
is set to Yes.
The production application data is resident on an logical volume manager
logical volume.
Complete the following to restore an application back to its original location.
From the Backup and DR Service management console, click
App Manager and select Applications from the drop-down menu.
The Applications page opens.
Select the application with the image that you want to restore
using mount and migrate capability. Then select Access from
the drop-down list at the bottom of the Applications page.
Select the image you need, and select Restore from the drop-down menu on
the right-hand side of the page.
The Restore page opens.
Select the Mount and Migrate option to restore with near-zero downtime.
Optionally, in Label, enter a label for the cloned application.
By default, the label is filled with the Clone - M&M label.
Click Pre-Flight Check. You see a status message about the
progress of the pre-flight check. If the pre-flight check fails,
you see an error message explaining why the pre-flight check failed.
Fix the issues in the error message and run the pre-flight check again.
Once the pre-flight check passes, the Submit button is enabled.
Click Submit. The mount and migrate process is initiated,
which results in a couple of jobs running in the background: the mount job
and the migrate job.
The mount job mounts the selected point-in-time image of the
file system application back to the same host and location from where
the data was captured. Once the image is mounted, the data becomes
available almost instantaneously to the business application,
thus providing near-zero RTO.
After the successful completion of the mount job, the system
auto-initiates the migrate job, which starts migrating the application data
from Backup and DR disks onto the product storage in real-time—
including the data changes.
Use mount and migrate to restore (migrate) data to an alternative server location
Images from any file system application can be restored using the mount
and migrate option if the following is true:
The Application and Details setting Prefer LVM on staging disk
is set to Yes.
The production application data is resident on an logical volume manager
logical volume.
Use these instructions to restore an application back to a different server
location.
From the Backup and DR Service management console, click
App Manager and select Applications from the drop-down menu.
The Applications page opens.
Select the application with the image that you want to restore
using mount and migrate capability. Then select Access from
the drop-down list at the bottom of the Applications page.
Select a point-in-time that you want the application to restore.
Select Clone from the list of access operations.
The Clone page opens.
Select a host where the file system application is to be restored.
Optionally, in Label, enter a label for the cloned application.
By default, the label is filled with the Clone - M&M label
From the Target VG Name drop-down list, select the Volume Group
that you want to migrate. The selected Volume Group must have enough
unallocated space in it to hold the volume.
Click Pre-Flight Check. You see a status message about the
progress of the pre-flight check. If the pre-flight check fails,
you see an error message explaining why the pre-flight check failed.
Fix the issues in the error message and re-run the pre-flight check.
Once pre-flight check passes, the Submit button is enabled.
Click Submit.
The mount and migrate process is initiated. This results in two jobs; the
mount job and the migrate job.
The mount job mounts the selected point-in-time image of the
file system application back to the same host and location from
where the data was captured. Once the image is mounted,
the data becomes available almost instantaneously to the
business application, thus providing near-zero RTO.
After the mount job has succeeded, the system auto-initiates the migrate
job, which starts migrating the application data from Backup and DR
disks onto the product storage in real-time—including the data changes.
The file system administrator guide to Backup and DR Service
This page is one in a series of pages specific to protecting and recovering
filesystems with Backup and DR Service.
You can find additional information in the following pages:
[[["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-25 UTC."],[[["\u003cp\u003eThe mount and migrate feature allows for the recovery of Linux file systems backed up into an LVM-based staging disk, ensuring near-zero downtime during restoration.\u003c/p\u003e\n"],["\u003cp\u003eFor file systems smaller than 1 TiB or not on LVM, the "Prefer LVM on Staging Disk" flag must be enabled to utilize LVM during the backup and DR staging process.\u003c/p\u003e\n"],["\u003cp\u003eRestoring data to the original server location or an alternative one is possible, with the prerequisite that the "Prefer LVM on Staging Disk" setting is set to "Yes" and the production application data resides on an LVM logical volume.\u003c/p\u003e\n"],["\u003cp\u003eThe mount and migrate process involves a mount job, which makes data instantly available, and a subsequent migrate job, which transfers data from Backup and DR disks to the product storage in real time.\u003c/p\u003e\n"],["\u003cp\u003eThe target volume group extent size during mount and migrate must be the same as the production volume group at backup, or it will default to 4MB if LVM isn't utilized.\u003c/p\u003e\n"]]],[],null,["# Mount and migrate a file system for instant recovery to any target\n\nThe file system mount and migrate feature is available for recovery of Linux\nfile systems that are backed up into a logical volume manager (LVM) based\nstaging disk---as LVM is used for the online migration during recovery.\nIf the source file system is less than 1 TiB or is not on a logical volume\nmanager, a flag **Prefer LVM on Staging Disk** needs to be set to force logical\nvolume manager onto the Backup and DR staging disk. Backups of file\nsystems that are larger than 1 TiB are automatically backed up in logical volume\nmanager format, regardless of whether the **Prefer LVM for Single Staging Disk**\noption is set or not.\n\nKnown limitations\n-----------------\n\nThe target volume group extent size must be identical to the production volume\ngroup at the time of backup. If the production system does not have LVM,\nthe staging disk uses a default extent size of 4 MB.\n\nUse mount and migrate to restore data back to the same server location\n----------------------------------------------------------------------\n\nThe following must be true for images from any file system application to be\nrestored using the mount and migrate option:\n\n- The **Application** and **Details** setting `Prefer LVM on Staging disk` is set to **Yes**.\n- The production application data is resident on an logical volume manager logical volume.\n\n| **Note:** You can also restore an application to an alternative server location.\n\nComplete the following to restore an application back to its original location.\n\n1. From the Backup and DR Service management console, click\n **App Manager** and select **Applications** from the drop-down menu.\n\n The **Applications** page opens.\n2. Select the application with the image that you want to restore\n using mount and migrate capability. Then select **Access** from\n the drop-down list at the bottom of the **Applications** page.\n\n3. Select the image you need, and select **Restore** from the drop-down menu on\n the right-hand side of the page.\n\n The **Restore** page opens.\n4. Select the **Mount and Migrate** option to restore with near-zero downtime.\n\n5. Optionally, in **Label** , enter a label for the cloned application.\n By default, the label is filled with the **Clone - M\\&M** label.\n\n6. Click **Pre-Flight Check** . You see a status message about the\n progress of the pre-flight check. If the pre-flight check fails,\n you see an error message explaining why the pre-flight check failed.\n Fix the issues in the error message and run the pre-flight check again.\n Once the pre-flight check passes, the **Submit** button is enabled.\n\n7. Click **Submit**. The mount and migrate process is initiated,\n which results in a couple of jobs running in the background: the mount job\n and the migrate job.\n\n The mount job mounts the selected point-in-time image of the\n file system application back to the same host and location from where\n the data was captured. Once the image is mounted, the data becomes\n available almost instantaneously to the business application,\n thus providing near-zero RTO.\n\nAfter the successful completion of the mount job, the system\nauto-initiates the migrate job, which starts migrating the application data\nfrom Backup and DR disks onto the product storage in real-time---\nincluding the data changes.\n\nUse mount and migrate to restore (migrate) data to an alternative server location\n---------------------------------------------------------------------------------\n\nImages from any file system application can be restored using the mount\nand migrate option if the following is true:\n\n- The **Application and Details** setting **Prefer LVM** on staging disk is set to **Yes**.\n- The production application data is resident on an logical volume manager\n logical volume.\n\n | **Note:** You can also restore an application to the same server location.\n\nUse these instructions to restore an application back to a different server\nlocation.\n\n1. From the Backup and DR Service management console, click\n **App Manager** and select **Applications** from the drop-down menu.\n\n The **Applications** page opens.\n2. Select the application with the image that you want to restore\n using mount and migrate capability. Then select **Access** from\n the drop-down list at the bottom of the **Applications** page.\n\n3. Select a point-in-time that you want the application to restore.\n\n4. Select **Clone** from the list of access operations.\n\n The **Clone** page opens.\n5. Select a host where the file system application is to be restored.\n\n6. Optionally, in **Label** , enter a label for the cloned application.\n By default, the label is filled with the **Clone - M\\&M** label\n\n7. From the **Target VG Name drop-down** list, select the **Volume Group**\n that you want to migrate. The selected **Volume Group** must have enough\n unallocated space in it to hold the volume.\n\n8. Click **Pre-Flight Check** . You see a status message about the\n progress of the pre-flight check. If the pre-flight check fails,\n you see an error message explaining why the pre-flight check failed.\n Fix the issues in the error message and re-run the pre-flight check.\n Once pre-flight check passes, the **Submit** button is enabled.\n\n9. Click **Submit**.\n\n The mount and migrate process is initiated. This results in two jobs; the\n mount job and the migrate job.\n\n The mount job mounts the selected point-in-time image of the\n file system application back to the same host and location from\n where the data was captured. Once the image is mounted,\n the data becomes available almost instantaneously to the\n business application, thus providing near-zero RTO.\n\n After the mount job has succeeded, the system auto-initiates the migrate\n job, which starts migrating the application data from Backup and DR\n disks onto the product storage in real-time---including the data changes.\n\nThe file system administrator guide to Backup and DR Service\n------------------------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nfilesystems with Backup and DR Service.\nYou can find additional information in the following pages:\n\n- [Backup and DR for file systems](/backup-disaster-recovery/docs/concepts/filesystem-intro)\n- [Manage hosts and their connected applications](/backup-disaster-recovery/docs/configuration/manage-hosts-and-their-connected-applications)\n- [Configure application details and settings to protect file system data](/backup-disaster-recovery/docs/backup/configure-app-settings-for-filesystems)\n- [Apply a backup plan to protect a file system](/backup-disaster-recovery/docs/create-plan/apply-backup-plan-to-filesystem)\n- [Restore a file system to the source](/backup-disaster-recovery/docs/access-data/filesystem-restore)\n- [Mount a file system or file share](/backup-disaster-recovery/docs/access-data/mount-file-system)\n- [Mount and migrate a file system for instant recovery to any target](/backup-disaster-recovery/docs/access-data/filesystem-mount-and-migrate)"]]