Unmounting backups

Contributors Download PDF of this page

SnapManager automatically unmounts the backup to make it unavailable to the host server. SnapManager also allows you to unmount if you are using an external tool, such as Oracle Recovery Manager (RMAN), to access the files in the backup, and to change the state of the backup to remove access.

If you are unmounting a database backup from a remote host, you must ensure that the Automatic Storage Management (ASM) credentials are same on both the hosts.

You can optionally collect the dump files after a successful or failed unmount backup operation.

The unmount operation might fail sometime with an error message if the mount point is busy, for example, --[ERROR] FLOW-11019: Failure in Disconnect: SD-10046: You cannot unmount the backup as the mount point is busy with the following mount paths and PID’s: /opt/NetApp/smo/mnt/-mnt-neuse_nfsvrdb_arch-20120427052319903_0 with PID 6598.

You must identify the PID of the session that is resulting in the failure of the unmount operation. Stop the session by running the following command: kill pid

You can then run the unmount operation successfully.

  1. Enter the following command: smo backup unmount -profile profile_name {labellabel [data | -archivelogs] | -idid} [-quiet | -verbose] -dump-force-verbose

Related information