NetBackup™ for Cloud Object Store Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (11.0)
  1. Introduction
    1.  
      Overview of NetBackup protection for Cloud object store
    2.  
      Features of NetBackup Cloud object store workload support
  2. Managing Cloud object store assets
    1.  
      Planning NetBackup protection for Cloud object store assets
    2.  
      Enhanced backup performance in 11.0 or later
    3.  
      Prerequisites for adding Cloud object store accounts
    4.  
      Configuring buffer size for backups
    5.  
      Configure a temporary staging location
    6.  
      Configuring advanced parameters for Cloud object store
    7.  
      Permissions required for Amazon S3 cloud provider user
    8.  
      Permissions required for Azure blob storage
    9.  
      Permissions required for GCP
    10.  
      Limitations and considerations
    11. Adding Cloud object store accounts
      1.  
        Creating cross-account access in AWS
      2.  
        Check certificate for revocation
      3.  
        Managing Certification Authorities (CA) for NetBackup Cloud
      4.  
        Adding a new region
    12.  
      Manage Cloud object store accounts
    13. Scan for malware
      1.  
        Backup images
      2.  
        Assets by policy type
  3. Protecting Cloud object store assets
    1. About accelerator support
      1.  
        How NetBackup accelerator works with Cloud object store
      2.  
        Accelerator notes and requirements
      3.  
        Accelerator force rescan for Cloud object store (schedule attribute)
      4.  
        Accelerator backup and NetBackup catalog
      5.  
        Calculate the NetBackup accelerator track log size
    2.  
      About incremental backup
    3.  
      About dynamic multi-streaming
    4. About storage lifecycle policies
      1.  
        Adding an SLP
    5.  
      About policies for Cloud object store assets
    6.  
      Planning for policies
    7.  
      Prerequisites for Cloud object store policies
    8.  
      Creating a backup policy
    9.  
      Policy attributes
    10.  
      Creating schedule attributes for policies
    11. Configuring the Start window
      1.  
        Adding, changing, or deleting a time window in a policy schedule
      2.  
        Example of schedule duration
    12.  
      Configuring the exclude dates
    13.  
      Configuring the include dates
    14.  
      Configuring the Cloud objects tab
    15.  
      Adding conditions
    16.  
      Adding tag conditions
    17.  
      Examples of conditions and tag conditions
    18. Managing Cloud object store policies
      1.  
        Copy a policy
      2.  
        Deactivating or deleting a policy
      3.  
        Manually backup assets
  4. Recovering Cloud object store assets
    1.  
      Prerequisites for recovering Cloud object store objects
    2.  
      Configuring Cloud object retention properties
    3.  
      Recovering Cloud object store assets
  5. Troubleshooting
    1.  
      Error 5541: Cannot take backup, the specified staging location does not have enough space
    2.  
      Error 5537: Backup failed: Incorrect read/write permissions are specified for the download staging path.
    3.  
      Error 5538: Cannot perform backup. Incorrect ownership is specified for the download staging path.
    4.  
      Reduced acceleration during the first full backup, after upgrade to versions 10.5 and 11.
    5.  
      After backup, some files in the shm folder and shared memory are not cleaned up.
    6.  
      After an upgrade to NetBackup version 10.5, copying, activating, and deactivating policies may fail for older policies
    7.  
      Backup fails with default number of streams with the error: Failed to start NetBackup COSP process.
    8.  
      Backup fails, after you select a scale out server or Snapshot Manager as a backup host
    9.  
      Backup fails or becomes partially successful on GCP storage for objects with content encoded as GZIP.
    10.  
      Recovery for the original bucket recovery option starts, but the job fails with error 3601
    11.  
      Recovery Job does not start
    12.  
      Restore fails: "Error bpbrm (PID=3899) client restore EXIT STATUS 40: network connection broken"
    13.  
      Access tier property not restored after overwriting the existing object in the original location
    14.  
      Reduced accelerator optimization in Azure for OR query with multiple tags
    15.  
      Backup failed and shows a certificate error with Amazon S3 bucket names containing dots (.)
    16.  
      Azure backup jobs fail when space is provided in a tag query for either tag key name or value.
    17.  
      The Cloud object store account has encountered an error
    18.  
      The bucket is list empty during policy selection
    19.  
      Creating a second account on Cloudian fails by selecting an existing region
    20.  
      Restore failed with 2825 incomplete restore operation
    21.  
      Bucket listing of a cloud provider fails when adding a bucket in the Cloud objects tab
    22.  
      AIR import image restore fails on the target domain if the Cloud store account is not added to the target domain
    23.  
      Backup for Azure Data Lake fails when a back-level media server is used with backup host or storage server version 10.3
    24.  
      Backup fails partially in Azure Data Lake: "Error nbpem (pid=16018) backup of client
    25.  
      Recovery for Azure Data Lake fails: "This operation is not permitted as the path is too deep"
    26.  
      Empty directories are not backed up in Azure Data Lake
    27.  
      Recovery error: "Invalid alternate directory location. You must specify a string with length less than 1025 valid characters"
    28.  
      Recovery error: "Invalid parameter specified"
    29.  
      Restore fails: "Cannot perform the COSP operation, skipping the object: [/testdata/FxtZMidEdTK]"
    30.  
      Cloud store account creation fails with incorrect credentials
    31.  
      Discovery failures due to improper permissions
    32.  
      Restore failures due to object lock

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://www.veritas.com/support/en_US/article.100073852.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_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

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.

Configuring the temporary staging location:

  • 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.