마운트 및 마이그레이션을 사용하면 애플리케이션이 실행 중일 때 애플리케이션 데이터를 즉시 복구하고 데이터를 프로덕션 스토리지로 실시간으로 마이그레이션하여 RTO를 거의 0으로 만들 수 있습니다. 애플리케이션 데이터를 원래 위치 또는 다른 서버로 복구할 수 있습니다.
마운트 및 이전 복구 기능을 사용하면 다음과 같은 이점이 있습니다.
최종 스토리지 대상에 대한 데이터 복구를 위한 거의 0에 가까운 RTO를 제공합니다.
서버 및 스토리지 이전의 다운타임을 줄입니다.
SQL Server와 논리 볼륨 관리자 파일 시스템 마운트 및 이전의 차이점
SQL 및 파일 시스템 애플리케이션에서 마운트 및 이전 기능을 사용할 수 있습니다.
마운트 및 이전이 구현된 방식에는 몇 가지 중요한 차이점이 있습니다.
파일 시스템 애플리케이션에 LVM (Logical Volume Manager)이 있으면 LVM이 데이터를 마이그레이션할 수 있으며 백업 및 DR은 마운트 및 마이그레이션 중에 이 기능을 활용합니다.
그러나 SQL 애플리케이션은 데이터를 이전할 수 없습니다. 백업 및 DR에서 SQL 마운트 및 마이그레이션을 위한 맞춤 마이그레이션 프로세스를 빌드했습니다.
LVM 파일 시스템 마운트 및 이전은 클론 및 복원 전용으로 구현된 두 단계 프로세스입니다. 반면 SQL Server 마운트 및 마이그레이션은 마운트 또는 복원, 마이그레이션 일정 구성, 마이그레이션 완료의 세 단계를 포함하는 전체 구현입니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 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)"]]
