Staging configuration for Cloud Object Store protection

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.

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 staging location: /usr/openv/netbackup/db/cos_tmp_staging_path is symlinked to mounted location /mnt/nbdata/usr/openv/netbackup/db/cos_tmp_staging_path
• For Flex:
  • The default temporary staging location for a media server: /usr/openv/netbackup/db/cos_tmp_staging_path is symlinked to the mounted location /mnt/nbstage/usr/openv/netbackup/db/cos_tmp_staging_path
• For the primary server:
  • The temporary staging path /usr/openv/netbackup/db/cos_tmp_staging_path is symlinked to the mounted location /mnt/nbdata/usr/openv/netbackup/db/cos_tmp_staging_path

It is recommended to use a 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.

Use the following guidelines for sizing of the temporary staging location:

• The minimum space requirement is 20 GB per job.
• To run faster backups of a size between 100 GB to 500 GB, the minimum space required is 50 GB per job.
• 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 it as the temporary staging location.

• Example command to mount RAM as a 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 the 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.

For all temporary staging locations:

• Ensure that there is enough free space at the location.
• The 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 is completed.
• Each backup host must have a different mount point for the temporary staging location.