Check staging disk format and backup method for other databases
Stay organized with collections
Save and categorize content based on your preferences.
These two settings determine the type of backup image that you get. It is
important to make sure they are set properly.
Ensure that the staging disk format is set correctly
You set the staging disk format when you added the host. Before continuing,
check the staging disk format to be sure that you can get the backup image type
that you need.
To check the staging disk format, follow these steps:
From Manage, Hosts list, right-click the host and select Edit.
Halfway down the Edit Host page, the Staging Disk Format is
either NFS or Block:
Block: Block-based staging disks are the most useful for both
Backup and DR and TDM usage. Backup and DR changed-block tracking
is only available on block-based staging disks, and virtual databases
can only be mounted to block-based staging disks.
NFS: NFS based staging disks permit only file-based backup with
Full+Incremental file system backup. Select NFS only if Block is
not an option in your network.
If the staging disk format is set incorrectly, change it now
and click Save before continuing.
Check the backup method to be used for this database or instance
The backup method determines the type of backup image you get, either
volume-level or file-based.
You set the backup method when you filled in the details and settings for this
database. Before continuing, check the backup method to ensure that you get the
backup image type you need.
To configure the database backup plan settings, follow these instructions:
Click App manager>Applications.
Right-click the database and select Manage backup plan.
Select Details & settings.
Go to Backup capture method. Choose between two backup methods:
Volume level backup: Use volume level logical volume manager snapshots
with change block tracking on Linux to a block-based staging disk. This
option lets you create application aware virtual databases from the
snapshot images. The production instance or database must be present on the
logical volume manager volume.
Full+Incremental backup: This is file-based backup and recovery.
This file dump method does not support the creation of virtual databases.
You can use this for both block and NFS staging disks. If you need to use NFS
staging disks, then use this backup method. For most purposes, volume-level
backup images are a better choice.
A virtual database can be protected individually and the protection
applies on the entire instance. You can include or exclude specific
databases during the process using a database inclusion rule from the
Manage backup plan pages.
Click Save at the bottom of the page if changes were made to your
settings.
[[["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-03 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)"]]
