Stay organized with collections
Save and categorize content based on your preferences.
Mount and migrate lets you recover application data instantly and
migrate the data in real-time to production storage while the application
is up and running, providing near-zero RTO. You can recover application data
to the original location or to another server.
Benefits of using the Mount and Migrate Recover feature include the
following:
Provides a near-zero RTO for data recovery back to the final
storage destination.
Reduces downtime for server and storage migrations.
Differences between SQL Server and logical volume manager file system mount and migrate
Mount and migrate capability is available for SQL and file system applications.
There are a few significant differences in the way mount and migrate was
implemented:
When a file system application has Logical Volume Manager (LVM) on it, the
LVM can migrate data and Backup and DR leverages this
capability during mount and migrate.
However, SQL applications cannot migrate data. Backup and DR has built a
custom migration process for SQL mount and migrate.
The LVM file system mount and migrate is a two-step process
that has been implemented for clone and restore only. By
contrast, the SQL Server mount and migrate is a full implementation
involving the three steps of mount or restore, configuring migration
schedule, and finalize migration.
Configure schedule for mount and migrate
Use the following instructions to configure migration schedules.
Configure migration schedule for mount—restore—images
Use these instructions to configure the migration schedule:
Select an active image with an image state of Mounted or Restore Mounted.
Select Migrate from the drop-down menu.
The Update Migrate Frequency page opens.
For Frequency, use the slider to define the frequency with which
to schedule migrate jobs—in hours. The minimum value is one hour
and the maximum value is 24 hours.
For Copy Thread Count, specify the number of parallel copy threads to
use, per disk volume, during the migration. The default value is four.
Click Submit. You are prompted to confirm.
Click Proceed to apply the configuration.
You can see a success message after configuration is complete.
Click Okay in the success dialog to the Active Mounts page.
Configure migration schedule for mounted images
Use these instructions to configure migration schedule:
Select an active image with an image state of mounted or restore mounted.
Select Migrate from the drop-down menu.
The Update Migrate Frequency page opens.
If you selected a Mount image, you can see the following dialog.
For a mounted image, you may see more options depending on the specific
database.
For Frequency, use the slider to define the frequency with which
to schedule migrate jobs—in hours. Minimum value is one
hour and the maximum value is 24 hours.
For Copy Thread Count, specify the number of parallel copy
threads to use, per disk volume, during the migration.
The default value is four.
In the File Locations section, specify whether you want
to copy the database files to the same path as the source server,
or to a new location. There are three options:
Copy files to the same drive or path as they were on the source
server—default option.
Choose new file locations at the volume level.
Choose new file locations at the file level.
If you select the second option—new file option at the volume
level—you see a table with the source volume—cannot be
edited—and target volume drop-down—which is pre-populated with
the same value as the source.
In Target Volume, select a target volumes from the drop-down
list of all discovered file system applications. If needed, you can
also type the volume, for example: M:\`, orL:\Logs\Log1`.
If you select the third option—new file locations at the file
level—you can see a table with three columns:
+ File: Cannot be edited.
+ Source Location: Cannot be edited.
+ Target Location: This is pre-populated with the same value as that of
the source location, excluding filename.
In Target Location, enter the new file location and make other
modifications as needed.
Click Submit. You are prompted to confirm.
Click Proceed to apply the configuration.
A success message displays after the configuration is complete.
Click Okay in the success dialog to the Active Mounts page.
[[["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-09-04 UTC."],[[["\u003cp\u003eThe Mount and Migrate feature enables near-zero RTO by allowing instant application data recovery and real-time migration to production storage while the application remains operational.\u003c/p\u003e\n"],["\u003cp\u003eMount and Migrate can be used for both SQL and file system applications, however, SQL applications use a custom migration process while file system applications with LVM leverage LVM for migration.\u003c/p\u003e\n"],["\u003cp\u003eThe migration schedule frequency for Mount and Migrate can be configured, allowing you to set jobs to run every 1 to 24 hours.\u003c/p\u003e\n"],["\u003cp\u003eWhen configuring the migration schedule, users can define the number of parallel copy threads per disk volume, with a default of four threads.\u003c/p\u003e\n"],["\u003cp\u003eUsers can choose to migrate database files to the same location as the source or to new file locations, either at the volume level or the file level.\u003c/p\u003e\n"]]],[],null,["# Mount and migrate SQL Server databases\n\nMount and migrate lets you recover application data instantly and\nmigrate the data in real-time to production storage while the application\nis up and running, providing near-zero RTO. You can recover application data\nto the original location or to another server.\n\nBenefits of using the **Mount** and **Migrate Recover** feature include the\nfollowing:\n\n- Provides a near-zero RTO for data recovery back to the final storage destination.\n- Reduces downtime for server and storage migrations.\n\nDifferences between SQL Server and logical volume manager file system mount and migrate\n---------------------------------------------------------------------------------------\n\nMount and migrate capability is available for SQL and file system applications.\nThere are a few significant differences in the way mount and migrate was\nimplemented:\n\n- When a file system application has Logical Volume Manager (LVM) on it, the LVM can migrate data and Backup and DR leverages this capability during mount and migrate. However, SQL applications cannot migrate data. Backup and DR has built a custom migration process for SQL mount and migrate.\n- The LVM file system mount and migrate is a two-step process that has been implemented for clone and restore only. By contrast, the SQL Server mount and migrate is a full implementation involving the three steps of mount or restore, configuring migration schedule, and finalize migration.\n\nConfigure schedule for mount and migrate\n----------------------------------------\n\nUse the following instructions to configure migration schedules.\n\n- [Configure migration schedule for mount---restore---images](#restore-image)\n- [Configure migration schedule for mounted images](#mount)\n\n### Configure migration schedule for mount---restore---images\n\nUse these instructions to configure the migration schedule:\n\n1. Select an active image with an image state of **Mounted** or **Restore Mounted**.\n2. Select **Migrate** from the drop-down menu.\n\n The **Update Migrate Frequency** page opens.\n3. For **Frequency**, use the slider to define the frequency with which\n to schedule migrate jobs---in hours. The minimum value is one hour\n and the maximum value is 24 hours.\n\n4. For **Copy Thread Count**, specify the number of parallel copy threads to\n use, per disk volume, during the migration. The default value is four.\n\n5. Click **Submit**. You are prompted to confirm.\n\n6. Click **Proceed** to apply the configuration.\n\n7. You can see a success message after configuration is complete.\n\n8. Click **Okay** in the success dialog to the **Active Mounts** page.\n\n### Configure migration schedule for mounted images\n\nUse these instructions to configure migration schedule:\n\n1. Select an active image with an image state of mounted or restore mounted.\n2. Select **Migrate** from the drop-down menu.\n\n The **Update Migrate Frequency** page opens.\n\n If you selected a **Mount** image, you can see the following dialog.\n For a mounted image, you may see more options depending on the specific\n database.\n3. For **Frequency**, use the slider to define the frequency with which\n to schedule migrate jobs---in hours. Minimum value is one\n hour and the maximum value is 24 hours.\n\n4. For **Copy Thread Count**, specify the number of parallel copy\n threads to use, per disk volume, during the migration.\n The default value is four.\n\n5. In the **File Locations** section, specify whether you want\n to copy the database files to the same path as the source server,\n or to a new location. There are three options:\n\n - Copy files to the same drive or path as they were on the source server---default option.\n - Choose new file locations at the volume level.\n - Choose new file locations at the file level.\n\n If you select the second option---new file option at the volume\n level---you see a table with the source volume---cannot be\n edited---and target volume drop-down---which is pre-populated with\n the same value as the source.\n\n In **Target Volume** , select a target volumes from the drop-down\n list of all discovered file system applications. If needed, you can\n also type the volume, for example: ``M:\\`, or``L:\\\\Logs\\\\Log1\\`.\n\n If you select the third option---new file locations at the file\n level---you can see a table with three columns:\n + **File** : Cannot be edited.\n + **Source Location** : Cannot be edited.\n + **Target Location**: This is pre-populated with the same value as that of\n the source location, excluding filename.\n6. In **Target Location**, enter the new file location and make other\n modifications as needed.\n\n7. Click **Submit**. You are prompted to confirm.\n\n8. Click **Proceed** to apply the configuration.\n A success message displays after the configuration is complete.\n\n9. Click **Okay** in the success dialog to the **Active Mounts** page.\n\nReview the following pages for more information:\n\n- [File system mount and migrate](/backup-disaster-recovery/docs/access-data/filesystem-mount-and-migrate)\n- [SQL Server mount and migrate](/backup-disaster-recovery/docs/access-data/sql-server-mount-and-migrate)"]]
