Stay organized with collections
Save and categorize content based on your preferences.
Generic applications can be mounted like any other application.
To mount a Generic App (LVM), follow these steps:
From the Backup and DR Service management console, click
App Manager and select Applications from the drop-down menu.
The Applications page opens.
Right-click the Generic App (LVM) application that you want to mount and
select Access.
Select a backup image and chose Mount.
If you are mounting to a regular host, leave the Host or VM option as
default.
If you want to mount to a Container use the instructions in the
Mount an image to a container.
Select the target host from the Host drop-down list.
Optionally, assign a Label to the mounted image.
If required, change the default storage pool to be used for the mount
from the Storage Pool drop-down list. This only applies to mounts where
there is no existing staging disk, such as imported OnVault images, otherwise
the snapshot pool where the source image disks are located are always used
regardless of what is set here.
Specify pre- and post-script paths for scripts that automates bringing
up and shutting down the databases associated with the Linux-based generic
application. Consult the administrator guide for your database to determine
the script names to be used and where they reside.
Select one of the following actions from the Mount Action drop-down menu:
Keep Source Path: Maintain the original folder structure.
Specify Mount Location: Specify a specific location to mount the
application.
Map Only: Map the volumes to a host without mounting into the file
system.
Select Submit. You can go to the Job Monitor to
view the progress and details of the job. The mounted image is
available in the Active Mounts.
Management of the active mounts
Once you have created a mount, you can track the image form the App Manager > Active Mounts.
Do not leave any image mounted indefinitely. This is because the
backup image that the mount was created from, cannot expire until all its mounts have
been deleted. When you have finished using the mounted image then either:
Unmount
the image. You can remount it if needed. You can then
delete
the image later when you are certain it is no longer needed.
Unmount and delete the image. This deletes the mounted
image, not the backup that the mount is based on.
[[["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-08-29 UTC."],[[["\u003cp\u003eGeneric applications can be mounted by navigating to the App Manager, selecting Applications, and choosing the desired Generic App (LVM) to access and mount.\u003c/p\u003e\n"],["\u003cp\u003eDuring the mounting process, users can select a backup image, target host, optional label, and storage pool, as well as specifying pre- and post-scripts for automation of the application.\u003c/p\u003e\n"],["\u003cp\u003eUsers can define the mount location and action, such as keeping the source path, specifying a specific location, or only mapping the volumes.\u003c/p\u003e\n"],["\u003cp\u003eActive mounts can be tracked via the App Manager, and users should unmount or unmount and delete the image when finished to allow for backup image expiration.\u003c/p\u003e\n"],["\u003cp\u003eIf mounting to a container, specific instructions are located at a designated URL, but if mounting to a regular host, the Host or VM option should remain default.\u003c/p\u003e\n"]]],[],null,["# Mount a Generic App (LVM)\n\nGeneric applications can be mounted like any other application.\n\nTo mount a **Generic App (LVM)**, follow these steps:\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. Right-click the **Generic App (LVM)** application that you want to mount and\n select **Access**.\n\n | **Note:** You can use the **Generic Apps (LVM)** filter to show the apps.\n3. Select a backup image and chose **Mount**.\n\n4. If you are mounting to a regular host, leave the **Host or VM** option as\n default.\n If you want to mount to a **Container** use the instructions in the\n [Mount an image to a container](/backup-disaster-recovery/docs/backup/consume-captured-app-data-in-a-container-environment).\n\n5. Select the target host from the **Host** drop-down list.\n\n6. Optionally, assign a **Label** to the mounted image.\n\n7. If required, change the default storage pool to be used for the mount\n from the **Storage Pool** drop-down list. This only applies to mounts where\n there is no existing staging disk, such as imported OnVault images, otherwise\n the snapshot pool where the source image disks are located are always used\n regardless of what is set here.\n\n8. Specify pre- and post-script paths for scripts that automates bringing\n up and shutting down the databases associated with the Linux-based generic\n application. Consult the administrator guide for your database to determine\n the script names to be used and where they reside.\n\n9. Select one of the following actions from the **Mount Action** drop-down menu:\n\n - **Keep Source Path**: Maintain the original folder structure.\n - **Specify Mount Location**: Specify a specific location to mount the application.\n - **Map Only**: Map the volumes to a host without mounting into the file system.\n10. Select **Submit** . You can go to the **Job Monitor** to\n view the progress and details of the job. The mounted image is\n available in the [Active Mounts](#active).\n\nManagement of the active mounts\n-------------------------------\n\nOnce you have created a mount, you can track the image form the **App Manager** \\\u003e **Active Mounts**.\nDo not leave any image mounted indefinitely. This is because the\nbackup image that the mount was created from, cannot expire until all its mounts have\nbeen deleted. When you have finished using the mounted image then either:\n\n- [Unmount](/backup-disaster-recovery/docs/access-data/manage-active-mounts#unmount) the image. You can [remount](/backup-disaster-recovery/docs/access-data/manage-active-mounts#remount) it if needed. You can then [delete](/backup-disaster-recovery/docs/access-data/manage-active-mounts#delete) the image later when you are certain it is no longer needed.\n- [Unmount and delete](/backup-disaster-recovery/docs/access-data/manage-active-mounts#unmount-delete) the image. This deletes the mounted image, not the backup that the mount is based on."]]
