Memeriksa format disk staging dan metode pencadangan untuk database lain
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Kedua setelan ini menentukan jenis image cadangan yang Anda dapatkan. Penting
untuk memastikannya ditetapkan dengan benar.
Pastikan format disk staging ditetapkan dengan benar
Anda menetapkan format disk staging saat menambahkan host. Sebelum melanjutkan,
periksa format disk staging untuk memastikan Anda bisa mendapatkan jenis image cadangan
yang Anda butuhkan.
Untuk memeriksa format disk staging, ikuti langkah-langkah berikut:
Dari Kelola, daftar Host, klik kanan host, lalu pilih Edit.
Di bagian tengah halaman Edit Host, Staging Disk Format adalah
NFS atau Block:
Block: Disk staging berbasis blok paling berguna untuk
penggunaan Pencadangan dan DR serta TDM. Pelacakan blok yang diubah Pencadangan dan DR
hanya tersedia di disk staging berbasis blok, dan database virtual
hanya dapat dipasang ke disk staging berbasis blok.
NFS: Disk staging berbasis NFS hanya mengizinkan pencadangan berbasis file dengan
pencadangan sistem file Full+Incremental. Pilih NFS hanya jika Blokir
bukan opsi di jaringan Anda.
Jika format disk staging ditetapkan dengan tidak benar, ubah sekarang
dan klik Simpan sebelum melanjutkan.
Periksa metode pencadangan yang akan digunakan untuk database atau instance ini
Metode pencadangan menentukan jenis image cadangan yang Anda dapatkan, baik
tingkat volume maupun berbasis file.
Anda menetapkan metode pencadangan saat mengisi detail dan setelan untuk database ini. Sebelum melanjutkan, periksa metode pencadangan untuk memastikan Anda mendapatkan
jenis image cadangan yang diperlukan.
Untuk mengonfigurasi setelan rencana pencadangan database, ikuti petunjuk berikut:
Klik App manager>Applications.
Klik kanan database, lalu pilih Kelola rencana pencadangan.
Pilih Detail & setelan.
Buka Metode pengambilan cadangan. Pilih antara dua metode pencadangan:
Pencadangan tingkat volume: Gunakan snapshot pengelola volume logis tingkat volume
dengan pelacakan blok perubahan di Linux ke disk staging berbasis blok. Opsi
ini memungkinkan Anda membuat database virtual yang mengetahui aplikasi dari
gambar snapshot. Instance atau database produksi harus ada di
volume pengelola volume logis.
Pencadangan Full+Inkremental: Ini adalah pencadangan dan pemulihan berbasis file.
Metode pembuangan file ini tidak mendukung pembuatan database virtual.
Anda dapat menggunakannya untuk disk staging blok dan NFS. Jika Anda perlu menggunakan disk staging NFS, gunakan metode pencadangan ini. Untuk sebagian besar tujuan, image cadangan
level volume adalah pilihan yang lebih baik.
Database virtual dapat dilindungi satu per satu dan perlindungan tersebut
diterapkan di seluruh instance. Anda dapat menyertakan atau mengecualikan database tertentu selama proses menggunakan aturan penyertaan database dari halaman Kelola rencana pencadangan.
Klik Simpan di bagian bawah halaman jika ada perubahan pada
setelan Anda.
[[["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-11 UTC."],[[["\u003cp\u003eStaging disk format, either Block or NFS, dictates the type of backup image and functionalities available, with Block being preferred for Backup, DR, and virtual databases.\u003c/p\u003e\n"],["\u003cp\u003eThe backup method, set during database setup, determines whether the backup is volume-level or file-based, each supporting different features like virtual databases and compatibility with different staging disk formats.\u003c/p\u003e\n"],["\u003cp\u003eVolume-level backups utilize logical volume manager snapshots and change block tracking on block-based staging disks, allowing for the creation of application-aware virtual databases.\u003c/p\u003e\n"],["\u003cp\u003eFull+Incremental backups are file-based, suitable for both Block and NFS staging disks, but do not support virtual database creation.\u003c/p\u003e\n"],["\u003cp\u003eDatabase protection typically applies to the entire Db2 instance, though specific databases can be included or excluded via a Database Inclusion Rule in the Manage backup plan, while virtual databases can be protected individually.\u003c/p\u003e\n"]]],[],null,["# Check staging disk format and backup method for other databases\n\nThese two settings determine the type of backup image that you get. It is\nimportant to make sure they are set properly.\n\nEnsure that the staging disk format is set correctly\n----------------------------------------------------\n\nYou set the staging disk format when you added the host. Before continuing,\ncheck the staging disk format to be sure that you can get the backup image type\nthat you need.\n\nTo check the staging disk format, follow these steps:\n\n1. From **Manage** , **Hosts** list, right-click the host and select **Edit**.\n\n2. Halfway down the **Edit Host** page, the **Staging Disk Format** is\n either **NFS** or **Block**:\n\n - **Block**: Block-based staging disks are the most useful for both\n Backup and DR and TDM usage. Backup and DR changed-block tracking\n is only available on block-based staging disks, and virtual databases\n can only be mounted to block-based staging disks.\n\n - **NFS** : NFS based staging disks permit only file-based backup with\n Full+Incremental file system backup. Select **NFS** only if **Block** is\n not an option in your network.\n\n3. If the staging disk format is set incorrectly, change it now\n and click **Save** before continuing.\n\n | **Note:** System databases on a root partition can be backed up as logical volume manager snapshots and later mounted as virtual databases, but they cannot be used in a **Restore** operation as the root partition cannot be unmounted. This needs manual restore and recovery from a standard mount back to the same host.\n\nCheck the backup method to be used for this database or instance\n----------------------------------------------------------------\n\nThe backup method determines the type of backup image you get, either\nvolume-level or file-based.\n\nYou set the backup method when you filled in the details and settings for this\ndatabase. Before continuing, check the backup method to ensure that you get the\nbackup image type you need.\n\nTo configure the database backup plan settings, follow these instructions:\n\n1. Click **App manager** \\\u003e **Applications**.\n\n2. Right-click the database and select **Manage backup plan**.\n\n3. Select **Details \\& settings**.\n\n4. Go to **Backup capture method**. Choose between two backup methods:\n\n - **Volume level backup**: Use volume level logical volume manager snapshots\n with change block tracking on Linux to a block-based staging disk. This\n option lets you create application aware virtual databases from the\n snapshot images. The production instance or database must be present on the\n logical volume manager volume.\n\n - **Full+Incremental backup**: This is file-based backup and recovery.\n This file dump method does not support the creation of virtual databases.\n You can use this for both block and NFS staging disks. If you need to use NFS\n staging disks, then use this backup method. For most purposes, volume-level\n backup images are a better choice.\n\n A virtual database can be protected individually and the protection\n applies on the entire instance. You can include or exclude specific\n databases during the process using a database inclusion rule from the\n **Manage backup plan** pages.\n5. Click **Save** at the bottom of the page if changes were made to your\n settings.\n\n| **Note:** With one exception, protection is set for the entire Db2 instance. You can include or exclude specific databases during the process using a **Database Inclusion Rule** from the **Manage Backup Plan** pages. The exception is that a virtual database can be protected individually.\n\nWhat's next\n-----------\n\n[Protect the database or instance and its logs](/backup-disaster-recovery/docs/backup/otherdb-protect)"]]
