Select a point-in-time image, then select Mount from the list of access
operations.
The Mount page opens where the Mount to Host or VM option is
selected by default.
Select the Container option.
Enter a unique name associated with the container mount in the Label
field.
Enter a single IP address or a range of IP addresses in the
Allowed IP Addresses field. Network addresses in the format a.b.c.d./n
are also supported.
Specifying IP addresses limits the number of hosts to only those with the IP
address that are allowed to access application data for NFS.
Leaving the IP address empty allows any host to access the application data.
For Included Volumes, all volumes are selected by default.
Enter the path where the image should be mounted to inside the container in
the Mount Location field. By default, this path
is the same as the source path.
Enter the path where the appliance should expose the logical volume of the
application over NFS in the NFS Export Path field.
If no path is specified, the system auto generates a path and
exposes the data over that path.
Click Submit.
Click Okay to close the dialog, or click Monitor to follow the
progress of the job in Monitor. Once the mount job is complete, the image
becomes active and is available in the Active mounts view of the
App Manager.
After a successful mount job, the data is available from the appliance
over NFS. In order to access it from your container, you need to add
some code to your container YAML definition. You can obtain this YAML code
from either of the following:
In order to consume the selected application's data from within the container
over NFS, the YAML code must be added to the container's YAML configuration
file.
Management of the active mounts
Once you have created a mount, you can track the image form the App Manager > Active Mounts.
Don't 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-25 UTC."],[[["\u003cp\u003eThis process outlines how to mount and access application data from supported database applications within a container environment, which involves navigating to the \u003cstrong\u003eApplications\u003c/strong\u003e page and selecting the desired application image.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003cstrong\u003eAccess\u003c/strong\u003e page displays captured images, allowing the selection of a point-in-time image to be mounted to a container by specifying the \u003cstrong\u003eContainer\u003c/strong\u003e option.\u003c/p\u003e\n"],["\u003cp\u003eUsers must define parameters for container mounts, including a unique label, allowed IP addresses for access, and the paths for mounting inside the container and exposing the logical volume over NFS.\u003c/p\u003e\n"],["\u003cp\u003eAfter submission and job completion, the mounted image becomes active and accessible via NFS from the appliance, with container YAML code available in the \u003cstrong\u003eJob Details\u003c/strong\u003e or \u003cstrong\u003eActive Mounts\u003c/strong\u003e pages.\u003c/p\u003e\n"],["\u003cp\u003eMounted images should be unmounted or unmounted and deleted when they are no longer needed to allow the expiration of their base backup images, which is managed through the \u003cstrong\u003eActive Mounts\u003c/strong\u003e page.\u003c/p\u003e\n"]]],[],null,["# Mount a backup image to a container\n\nTo mount and access application data captured from valid application types\nin a container environment, follow these steps:\n\n1. From the Backup and DR Service management console, click\n **App Manager** \\\u003e **Applications** from the drop-down menu.\n\n The **Applications** page opens.\n2. Filter applications to list supported database applications---on Linux\n platform.\n\n | **Note:** The mount to containers capability is not available for Compute Engine instance, databases backups created using the Full+Incremental backup method, Oracle database backups, VMware VM backups, Windows application backups---SMB, file systems, and SQL server.\n3. Select the application with the chosen image.\n\n4. Choose **Access** from the drop-down list at the bottom of the\n **Applications** page.\n\n The **Access** page opens listing captured images in the timeline ramp view.\n For more information on this view, see\n [Access the timeline ramp view of an image](/backup-disaster-recovery/docs/access-data/access-image-copy-data-list#access-time).\n5. Select a point-in-time image, then select **Mount** from the list of access\n operations.\n\n The **Mount** page opens where the **Mount to Host or VM** option is\n selected by default.\n6. Select the **Container** option.\n\n7. Enter a unique name associated with the container mount in the **Label**\n field.\n\n8. Enter a single IP address or a range of IP addresses in the\n **Allowed IP Addresses** field. Network addresses in the format `a.b.c.d./n`\n are also supported.\n Specifying IP addresses limits the number of hosts to only those with the IP\n address that are allowed to access application data for NFS.\n\n Leaving the IP address empty allows any host to access the application data.\n9. For **Included Volumes**, all volumes are selected by default.\n\n - Enter the path where the image should be mounted to inside the container in the **Mount Location** field. By default, this path is the same as the source path.\n - Enter the path where the appliance should expose the logical volume of the application over NFS in the **NFS Export Path** field. If no path is specified, the system auto generates a path and exposes the data over that path.\n10. Click **Submit**.\n\n11. Click **Okay** to close the dialog, or click **Monitor** to follow the\n progress of the job in **Monitor** . Once the mount job is complete, the image\n becomes active and is available in the [Active mounts](#active) view of the\n **App Manager**.\n\n After a successful mount job, the data is available from the appliance\n over NFS. In order to access it from your container, you need to add\n some code to your container YAML definition. You can obtain this YAML code\n from either of the following:\n - The **Job Details** page, see [Monitor mount jobs to containers](/backup-disaster-recovery/docs/monitor-reports/monitor-jobs#container).\n - The **Active Mounts** page, see [Access container YAML code from the active mounts page](/backup-disaster-recovery/docs/access-data/access-image-copy-data-list#access-yaml).\n\nIn order to consume the selected application's data from within the container\nover NFS, the YAML code must be added to the container's YAML configuration\nfile.\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**.\nDon't 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."]]
