Memasang dan memigrasikan sistem file untuk pemulihan instan ke target mana pun
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Fitur pemasangan dan migrasi sistem file tersedia untuk pemulihan sistem file Linux yang dicadangkan ke disk penyiapan berbasis logical volume manager (LVM), karena LVM digunakan untuk migrasi online selama pemulihan.
Jika sistem file sumber berukuran kurang dari 1 TiB atau tidak berada di pengelola volume logis, tanda Prefer LVM on Staging Disk harus disetel untuk memaksakan pengelola volume logis ke disk penahapan Backup dan DR. Pencadangan sistem file yang berukuran lebih dari 1 TiB akan dicadangkan secara otomatis dalam format logical volume manager, terlepas dari apakah opsi Prefer LVM for Single Staging Disk disetel atau tidak.
Batasan umum
Ukuran alokasi grup volume target harus sama dengan grup volume produksi pada saat pencadangan. Jika sistem produksi tidak memiliki LVM, disk penyiapan menggunakan ukuran jangkauan default 4 MB.
Gunakan pasang dan migrasikan untuk memulihkan data kembali ke lokasi server yang sama
Berikut ini harus benar agar gambar dari aplikasi sistem file mana pun dapat dipulihkan menggunakan opsi pasang dan migrasikan:
Setelan Application dan DetailsPrefer LVM on Staging disk
disetel ke Yes.
Data aplikasi produksi berada di volume logis
pengelola volume logis.
Selesaikan langkah-langkah berikut untuk memulihkan aplikasi kembali ke lokasi aslinya.
Dari konsol pengelolaan Layanan Pencadangan dan DR, klik
Pengelola Aplikasi, lalu pilih Aplikasi dari menu drop-down.
Halaman Applications akan terbuka.
Pilih aplikasi dengan gambar yang ingin Anda pulihkan menggunakan kemampuan pemasangan dan migrasi. Kemudian, pilih Akses dari
daftar drop-down di bagian bawah halaman Aplikasi.
Pilih gambar yang Anda butuhkan, lalu pilih Pulihkan dari menu drop-down di
sisi kanan halaman.
Halaman Restore akan terbuka.
Pilih opsi Pasang dan Migrasikan untuk memulihkan dengan waktu henti hampir nol.
Secara opsional, di Label, masukkan label untuk aplikasi yang di-clone.
Secara default, label diisi dengan label Clone - M&M.
Klik Pre-Flight Check. Anda akan melihat pesan status tentang
progres pemeriksaan awal. Jika pemeriksaan awal gagal,
Anda akan melihat pesan error yang menjelaskan alasan pemeriksaan awal gagal.
Perbaiki masalah dalam pesan error dan jalankan pemeriksaan awal lagi.
Setelah pemeriksaan pra-peluncuran berhasil, tombol Kirim akan diaktifkan.
Klik Kirim. Proses pemasangan dan migrasi dimulai,
yang menghasilkan beberapa tugas yang berjalan di latar belakang: tugas pemasangan
dan tugas migrasi.
Tugas pemasangan memasang image titik waktu tertentu yang dipilih dari aplikasi sistem file kembali ke host dan lokasi yang sama tempat data diambil. Setelah gambar di-mount, data akan tersedia hampir secara instan untuk aplikasi bisnis, sehingga memberikan RTO yang mendekati nol.
Setelah tugas pemasangan berhasil diselesaikan, sistem akan otomatis memulai tugas migrasi, yang akan mulai memigrasikan data aplikasi dari disk Backup dan DR ke penyimpanan produk secara real-time, termasuk perubahan data.
Menggunakan pasang dan migrasikan untuk memulihkan (memigrasikan) data ke lokasi server alternatif
Image dari aplikasi sistem file apa pun dapat dipulihkan menggunakan opsi pasang dan migrasikan jika hal berikut benar:
Setelan Aplikasi dan DetailLebih suka LVM di disk staging
disetel ke Ya.
Data aplikasi produksi berada di volume logis
pengelola volume logis.
Gunakan petunjuk ini untuk memulihkan aplikasi kembali ke lokasi server yang berbeda.
Dari konsol pengelolaan Layanan Pencadangan dan DR, klik
Pengelola Aplikasi, lalu pilih Aplikasi dari menu drop-down.
Halaman Applications akan terbuka.
Pilih aplikasi dengan gambar yang ingin Anda pulihkan menggunakan kemampuan pemasangan dan migrasi. Kemudian, pilih Akses dari
daftar drop-down di bagian bawah halaman Aplikasi.
Pilih titik waktu yang ingin Anda pulihkan aplikasinya.
Pilih Clone dari daftar operasi akses.
Halaman Clone akan terbuka.
Pilih host tempat aplikasi sistem file akan dipulihkan.
Secara opsional, di Label, masukkan label untuk aplikasi yang di-clone.
Secara default, label diisi dengan label Clone - M&M
Dari daftar Target VG Name drop-down, pilih Volume Group
yang ingin Anda migrasikan. Grup Volume yang dipilih harus memiliki ruang yang tidak dialokasikan yang cukup untuk menampung volume.
Klik Pre-Flight Check. Anda akan melihat pesan status tentang
progres pemeriksaan awal. Jika pemeriksaan awal gagal,
Anda akan melihat pesan error yang menjelaskan alasan pemeriksaan awal gagal.
Perbaiki masalah dalam pesan error dan jalankan kembali pemeriksaan pra-peluncuran.
Setelah pemeriksaan pra-peluncuran berhasil, tombol Kirim akan diaktifkan.
Klik Kirim.
Proses pemasangan dan migrasi dimulai. Hal ini akan menghasilkan dua tugas; tugas pemasangan dan tugas migrasi.
Tugas pemasangan memasang image titik waktu tertentu yang dipilih dari aplikasi sistem file kembali ke host dan lokasi yang sama tempat data diambil. Setelah gambar di-mount, data akan tersedia hampir secara instan untuk aplikasi bisnis, sehingga memberikan RTO yang mendekati nol.
Setelah tugas pemasangan berhasil, sistem akan otomatis memulai tugas migrasi, yang akan mulai memigrasikan data aplikasi dari disk Backup and DR ke penyimpanan produk secara real-time—termasuk perubahan data.
Panduan administrator sistem file untuk Backup and DR Service
Halaman ini adalah salah satu dari serangkaian halaman khusus untuk melindungi dan memulihkan sistem file dengan Layanan Backup dan DR.
Anda dapat menemukan informasi tambahan di halaman berikut:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 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)"]]
