> [!CAUTION]
> **Caution:** Support for backing up and restoring workloads managed using the legacy appliance management console is deprecated. For more information, see [Feature deprecations](https://docs.cloud.google.com/backup-disaster-recovery/docs/deprecations.md.txt) in the Backup and DR documentation.

Generic applications can be mounted like any other application in the appliance management console.

To mount a **Generic App (LVM)**, follow these steps:

1. From the Backup and DR appliance management console, click
   **App Manager** and select **Applications** from the drop-down menu.

   The **Applications** page opens.
2. Right-click the **Generic App (LVM)** application that you want to mount and
   select **Access**.

   > [!NOTE]
   > **Note:** You can use the **Generic Apps (LVM)** filter to show the apps.

3. Select a backup image and chose **Mount**.

4. 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](https://docs.cloud.google.com/backup-disaster-recovery/docs/backup/consume-captured-app-data-in-a-container-environment).

5. Select the target host from the **Host** drop-down list.

6. Optionally, assign a **Label** to the mounted image.

7. 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.

8. 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.

9. 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.
10. 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](https://docs.cloud.google.com/backup-disaster-recovery/management-console/access-data/mount-generic-applications.md.txt#active).

## 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](https://docs.cloud.google.com/backup-disaster-recovery/management-console/access-data/manage-active-mounts.md.txt#unmount) the image. You can [remount](https://docs.cloud.google.com/backup-disaster-recovery/management-console/access-data/manage-active-mounts.md.txt#remount) it if needed. You can then [delete](https://docs.cloud.google.com/backup-disaster-recovery/management-console/access-data/manage-active-mounts.md.txt#delete) the image later when you are certain it is no longer needed.
- [Unmount and delete](https://docs.cloud.google.com/backup-disaster-recovery/management-console/access-data/manage-active-mounts.md.txt#unmount-delete) the image. This deletes the mounted image, not the backup that the mount is based on.