-f mount

This command mounts a snapshot backup on a backup system.

Mounting a backup means the following occurs:

Configure the target volumes, which might need to be assigned to the offload system (see the profile parameter BACKUP_HOST_NAME in DEVICE_CLASS device for details).
Import the volume groups from the target volumes.
Mount all file systems within the volume groups.

The mount is done by one mount agent for each backup server. As a result, a mount agent is started by the launchpad daemon that runs on the respective backup server. By specifying more options (filter arguments) such as,

 -i <instance-name>
 -d <database-name>
 -B <backup-id>

a specific snapshot backup can be selected for mounting on the offload system.

If no backup with the usability state TAPE_BACKUP_PENDING exists, the -B parameter is mandatory. Here are two examples. The first one is generic:

fcmcli -f mount -U <client_section_name> -B <backup-id>

fcmcli -f mount -d <database-name> -i <instance-name> -B <backup-id>.

Here is a specific example:

fcmcli -f mount -d DB1 -i db2db1 -B 20151020131727.

Note: If the option -B is omitted, the oldest backup still in state tape_backup_pending is selected implicitly.

(DB2®) In a DPF environment with multiple partitions, IBM Storage Protect Snapshot always mounts all partitions that are associated with a snapshot backup operation.

To reflect whether a snapshot backup is being mounted or is mounted, the usability states MOUNTING and MOUNTED, are set for those backups in the snapshot backup repository. These two state values prevent a duplicate mount request for a backup that is being mounted, or is already mounted, on the backup system. If multiple snapshot backups of a database are candidates to be mounted, IBM Storage Protect Snapshot picks the one with the most recent snapshot backup ID.