Configure a temporary staging location
This configuration is applicable only for Cloud object store protection using dynamic multi-streaming and backup hosts of NetBackup version 11.0 or later.
Enhanced Dynamic multi-streaming backup in NetBackup 11.0, or later, uses a staging location to exchange object data between the object store reader and NetBackup data mover. This staging location must be a filesystem path on the Cloud object store backup host. The storage space on the staging location is reclaimed during the course of a backup as and when the object data and metadata are moved to the backup target. You can configure the storage space and water mark value depending upon the object store environment that you are protecting.
For more information about configuring the temporary storage location, see the Knowledge article:
https://support.cohesity.com/s/article/article-100073852.html.html
Default paths:
For BYO default path is:
/usr/openv/netbackup/db/cos_tmp_staging_path.For Cloud scale primary and media server: The default temporary stagging location:
/usr/openv/netbackup/db/cos_tmp_staging_pathis symlinked to mounted location/mnt/nbdata/usr/openv/netbackup/db/cos_tmp_staging_pathFor Flex:
The default temporary staging location for a media server:
/usr/openv/netbackup/db/cos_tmp_staging_pathis symlinked to the mounted location/mnt/nbstage/usr/openv/netbackup/db/cos_tmp_staging_pathFor the primary server:
The temporary staging path
/usr/openv/netbackup/db/cos_tmp_staging_pathis symlinked to the mounted location/mnt/nbdata/usr/openv/netbackup/db/cos_tmp_staging_path
For backup host other than Flex, it is recommended to use different path than the default path as it may not comply with the storage requirements. It is also recommended to create a different mount point with enough space. Backup performance is affected if the minimum required space is not available.
Note:
Ensure that the automount configuration entry is updated on the backup host, if you are using a different path other than the default.
Use the following guidelines for sizing of the temporary staging location on a backup host:
The minimum space requirement is 20 GB per backup job per bucket or container being backed up by the backup host.
For increased backup speed, you can configure 100 GB to 500 GB space for staging.
The device used for the temporary staging location must have high read and write throughput. It is recommended to use an SSD. If you still experience slow disk I/O throughput, mount RAM as a disk, and configure as the temporary staging location.
Here is an example command to mount RAM as disk:
sudo mount -t tmpfs -o size=64G tmpfs /mnt/tmp
For 64 GB and 128-GB RAM setups, it is recommend mounting half of RAM as a disk. For a 32-GB RAM setup, it is not recommended to mount RAM as a disk, as low backup performance is expected on large size objects.
Ensure that there is enough free space at the location.
File path should have only ASCII Characters.
Ensure that the NetBackup service user is the owner of the storage location and has 0700 permissions. Writing fails if the permissions are set to anything other than 0700.
The temporary staging location is cleaned up once a backup completes.
Each backup host must have a different mount point for the temporary staging location.
Optionally, you can set the following parameters in the bp.conf file in each backup host, to configure the temporary staging location.