NetBackup™ for Cloud Object Store Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.5)
  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.  
      Prerequisites for adding Cloud object store accounts
    3.  
      Configuring buffer size for backups
    4.  
      Permissions required for Amazon S3 cloud provider user
    5.  
      Permissions required for Azure blob storage
    6.  
      Permissions required for GCP
    7.  
      Limitations and considerations
    8. 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
    9.  
      Manage Cloud object store accounts
    10. 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 policies for Cloud object store assets
    5.  
      Planning for policies
    6.  
      Prerequisites for Cloud object store policies
    7.  
      Creating a backup policy
    8.  
      Policy attributes
    9.  
      Creating schedule attributes for policies
    10. Configuring the Start window
      1.  
        Adding, changing, or deleting a time window in a policy schedule
      2.  
        Example of schedule duration
    11.  
      Configuring the exclude dates
    12.  
      Configuring the include dates
    13.  
      Configuring the Cloud objects tab
    14.  
      Adding conditions
    15.  
      Adding tag conditions
    16.  
      Examples of conditions and tag conditions
    17. 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.  
      Reduced acceleration during the first full backup, after upgrade to version 10.5
    2.  
      After backup, some files in the shm folder and shared memory are not cleaned up.
    3.  
      After an upgrade to NetBackup version 10.5, copying, activating, and deactivating policies may fail for older policies
    4.  
      Backup fails with default number of streams with the error: Failed to start NetBackup COSP process.
    5.  
      Backup fails or becomes partially successful on GCP storage for objects with content encoding as GZIP.
    6.  
      Recovery for the original bucket recovery option starts, but the job fails with error 3601
    7.  
      Recovery Job does not start
    8.  
      Restore fails: "Error bpbrm (PID=3899) client restore EXIT STATUS 40: network connection broken"
    9.  
      Access tier property not restored after overwriting the existing object in the original location
    10.  
      Reduced accelerator optimization in Azure for OR query with multiple tags
    11.  
      Backup failed and shows a certificate error with Amazon S3 bucket names containing dots (.)
    12.  
      Azure backup jobs fail when space is provided in a tag query for either tag key name or value.
    13.  
      The Cloud object store account has encountered an error
    14.  
      The bucket is list empty during policy selection
    15.  
      Creating a second account on Cloudian fails by selecting an existing region
    16.  
      Restore failed with 2825 incomplete restore operation
    17.  
      Bucket listing of a cloud provider fails when adding a bucket in the Cloud objects tab
    18.  
      AIR import image restore fails on the target domain if the Cloud store account is not added to the target domain
    19.  
      Backup for Azure Data Lake fails when a back-level media server is used with backup host or storage server version 10.3
    20.  
      Backup fails partially in Azure Data Lake: "Error nbpem (pid=16018) backup of client
    21.  
      Recovery for Azure Data Lake fails: "This operation is not permitted as the path is too deep"
    22.  
      Empty directories are not backed up in Azure Data Lake
    23.  
      Recovery error: "Invalid alternate directory location. You must specify a string with length less than 1025 valid characters"
    24.  
      Recovery error: "Invalid parameter specified"
    25.  
      Restore fails: "Cannot perform the COSP operation, skipping the object: [/testdata/FxtZMidEdTK]"
    26.  
      Cloud store account creation fails with incorrect credentials
    27.  
      Discovery failures due to improper permissions
    28.  
      Restore failures due to object lock

Restore fails: "Cannot perform the COSP operation, skipping the object: [/testdata/FxtZMidEdTK]"

Explanation

Restore jobs fail when the files or directories that are uploaded to Azure Data Lake Gen2 account using DFS API's Overwrite function, replacing the original files.

In the nbcosp logs as you can see the error:

 *RESPONSE ERROR (ServiceCode=BlobOperationNotSupported) =====\nDescription=Blob operation is not supported.

Note:

In this issue, files that are uploaded to Azure portal using the Upload option are not included.

Workaround

Do any of the following:

  • Try restore operation on the same container to a different directory.

  • Try restore operation to a different container.

  • Try restore operation to a different destination.

  • Delete the original directory, and then try to restore to the same location.