NetBackup™ for Cloud Object Store Administrator's Guide

Last Published:
Product(s): NetBackup (11.1)
  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 dynamic multi-streaming parameters
    7.  
      Permissions required for Amazon S3 cloud provider user
    8.  
      Permissions required for Azure blob storage
    9.  
      Permission required for Azure Data Lake Storage
    10.  
      Permissions required for GCP
    11.  
      Limitations and considerations
    12. 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
    13.  
      Manage Cloud object store accounts
    14. 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 object change tracking
      1.  
        Configuring object change tracking
      2.  
        Configuring access permissions for the buckets
      3.  
        Configuring access policy on the log bucket
      4.  
        Configuration guidelines for IBM Storage Ceph
      5.  
        Enable bucket logging for source buckets
      6.  
        Creating policy for the log bucket
      7.  
        Additional storage requirements at the staging location
      8.  
        Configuring bucket logging in IBM Storage Ceph
      9.  
        Maintaining the log bucket
      10.  
        Configuring NetBackup for object change tracking
      11.  
        Configuring NetBackup policy for object change tracking
      12.  
        Verifying object change tracking in the Activity monitor
      13.  
        Scenarios when NetBackup overrides object change tracking
    5. About storage lifecycle policies
      1.  
        Adding an SLP
    6.  
      About policies for Cloud object store assets
    7.  
      Planning for policies
    8.  
      Prerequisites for Cloud object store policies
    9.  
      Creating a backup policy
    10.  
      Policy attributes
    11.  
      Creating schedule attributes for policies
    12. Configuring the Start window
      1.  
        Adding, changing, or deleting a time window in a policy schedule
      2.  
        Example of schedule duration
    13.  
      Configuring the exclude dates
    14.  
      Configuring the include dates
    15.  
      Configuring the Cloud objects tab
    16.  
      Adding conditions
    17.  
      Adding tag conditions
    18.  
      Examples of conditions and tag conditions
    19. 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 5549: Cannot validate bucket logging information
    2.  
      Error 5576: The maximum number of concurrent jobs specified for a storage unit, must be greater than or equal to the number of streams specified in the policy.
    3.  
      Error 5579: Falling back to object listing for change detection, not considering object change tracking for this bucket, specified in the policy.
    4.  
      Error 5580: The specified failover strategy for the storage unit group is incompatible with the Cloud object store policy, with dynamic multi-streaming.
    5.  
      Error 5545: Backup failed as NetBackup cannot parse records from the log object
    6.  
      Error 5541: Cannot take backup, the specified staging location does not have enough space
    7.  
      Error 5537: Backup failed: Incorrect read/write permissions are specified for the download staging path.
    8.  
      Error 5538: Cannot perform backup. Incorrect ownership is specified for the download staging path.
    9.  
      Reduced acceleration during the first full backup, after upgrade to versions 10.5 and 11.
    10.  
      After backup, some files in the shm folder and shared memory are not cleaned up.
    11.  
      After an upgrade to NetBackup version 10.5, copying, activating, and deactivating policies may fail for older policies
    12.  
      Backup fails with default number of streams with the error: Failed to start NetBackup COSP process.
    13.  
      Backup fails, after you select a scale out server or Snapshot Manager as a backup host
    14.  
      Backup fails or becomes partially successful on GCP storage for objects with content encoded as GZIP.
    15.  
      Recovery for the original bucket recovery option starts, but the job fails with error 3601
    16.  
      Recovery Job does not start
    17.  
      Restore fails: "Error bpbrm (PID=3899) client restore EXIT STATUS 40: network connection broken"
    18.  
      Access tier property not restored after overwriting the existing object in the original location
    19.  
      Reduced accelerator optimization in Azure for OR query with multiple tags
    20.  
      Backup failed and shows a certificate error with Amazon S3 bucket names containing dots (.)
    21.  
      Azure backup jobs fail when space is provided in a tag query for either tag key name or value.
    22.  
      The Cloud object store account has encountered an error
    23.  
      The bucket is list empty during policy selection
    24.  
      Creating a second account on Cloudian fails by selecting an existing region
    25.  
      Restore failed with 2825 incomplete restore operation
    26.  
      Bucket listing of a cloud provider fails when adding a bucket in the Cloud objects tab
    27.  
      AIR import image restore fails on the target domain if the Cloud store account is not added to the target domain
    28.  
      Backup for Azure Data Lake fails when a back-level media server is used with backup host or storage server version 10.3
    29.  
      Backup fails partially in Azure Data Lake: "Error nbpem (pid=16018) backup of client
    30.  
      Recovery for Azure Data Lake fails: "This operation is not permitted as the path is too deep"
    31.  
      Empty directories are not backed up in Azure Data Lake
    32.  
      Recovery error: "Invalid alternate directory location. You must specify a string with length less than 1025 valid characters"
    33.  
      Recovery error: "Invalid parameter specified"
    34.  
      Restore fails: "Cannot perform the COSP operation, skipping the object: [/testdata/FxtZMidEdTK]"
    35.  
      Cloud store account creation fails with incorrect credentials
    36.  
      Discovery failures due to improper permissions
    37.  
      Restore failures due to object lock

Recovering Cloud object store assets

You can recover Cloud object store assets to the original or a different bucket or container. You can also restore each of the objects to different buckets or containers.

To recover assets:

  1. On the left, click Recovery. Under Regular recovery, click Start recovery.
  2. In the Basic properties page, select Policy type as Cloud-Object-Store.
  3. Click the Buckets/Containers field to select assets to restore.
    • In the Add bucket/container dialog, the default option displays all available bucket/containers with completed backups. You can search the table using the search box.

    • To add a specific bucket or container, select Add the bucket/container details option. If you have selected an Azure Data Lake workload, select Add files/directories.

      Select the cloud provider, and enter the bucket/container name, and the Cloud object store account name. For Azure workloads, specify the storage account name, if available in the UI.

      Note:

      In a rare scenario, if you cannot find the required bucket listed in the table for selection. But you can see the same bucket listed in the catalog view as a backup ID. You can select the bucket by manually entering the bucket name, provider ID, and the Cloud object store account name as per the backup ID. The backup ID is formed as <providerId>_<cloudAccountname>_<uniquename>_<timestamp>

      for Azure the uniquename is storageaccountname.bucketname, and for S3 providers it is the bucket name.

  4. Click Add, and then click Next.
  5. In the Add objects page, select the Start date and the End date of the period from which you want to restore.

    (Optionally) Enter a keyword phrase to filter the images, and click Apply.

  6. Click Backup history, and select the required images for recovery from the Backup history dialog. Click Select.
  7. In the Recovery details page, you can add the objects and folders or prefix and scan the selected images for malware before restoring the images:
    • (Optional) Click Add objects and folders, and select the required objects to recover from the Add Object/blobs and folders dialog. Select Include all objects/blobs and folders to include all available assets. For an Azure Data Lake workload, this option is available as Include all files/directories. You can use the left navigation tree structure to filter the table. Click Add.

      The following warning message is displayed when images which are not scanned are selected for recovery:

      One or more images selected for recovery are not scanned.

      Note:

      To restore from malware-affected images, you must have the Administrator role or equivalent RBAC permissions.

      For more information on recovering from malware infected images, see Security and Encryption Guide.

    • (Optionally) Click Add prefix. In the Add prefix dialog, enter a prefix in the search box to display relevant results in the table. Click Add, to select all the matching prefixes displayed in the table for recovery. The selected prefixes are displayed in a table below the selected objects/blobs. Click Next.

    Note:

    Clean file recovery (Skip infected files) as part of recovery is not supported for Cloud-Object-Store.

  8. In the Recovery options page, you can select whether you want to restore to the source bucket of the container or use a different one. These are the Object restore options:
    • Restore to the original bucket or container: Select to recover to the same bucket or container from where the backup was taken.

      Optionally:

      • Add a prefix for the recovered assets in the Add a prefix field.

      • If you have selected an Azure Data Lake workload, enter the Directory to restore.

    • Restore to a different bucket or container: Select to recover to a different bucket or container than the one from where the backup was taken.

      • You can select a different Cloud object store account as the destination, from the list above.

      • Select a destination Bucket/Container name. You can use different Cloud object store accounts that can access the original bucket. This method also helps you create accounts with limited and specific permissions for backup and restore. In this case, you can provide the same bucket as the original to restore to the original bucket/container.

      • Optionally, add a prefix for the recovered assets in the Add a prefix field.

    • Restore object/blobs or prefixes to different destinations: Select to recover each of your selected assets to different destinations.

      • You can select a different Cloud object store account as the destination from the list.

      • Click Edit object destination, enter the Destination and Destination bucket/container name. Click Save.

      Note:

      If you have selected Include all objects/blobs and folders, in step 7, the Restore objects/blobs or prefixes to different destinations option is disabled.

  9. Select a Recovery host. The recovery host that is associated with the Cloud object store account is displayed by default. If required, change the Backup host. If the Cloud object store account uses a scale-out server, this field is disabled.
  10. Optionally, to overwrite any existing object or blobs using the recovered assets, select Overwrite existing objects/blobs.
  11. (Optional) To override the default priority of the restore job, select Override default priority, and assign the required value.
  12. In the Advanced restore options:
    • To apply the original object lock attributes from the backed-up objects, select Retain original object lock properties.

    • To change the values of different properties, select Customize object lock properties. From the Object lock mode list:

      • Select Compliance or Governance for Amazon or other S3 workloads.

      • Select Locked or Unlocked for Azure workloads.

      • Select a future date and time till which the object lock is valid. Note that the recovered object is locked till this specified date and time.

    • Select Object lock legal hold status to implement it on the restored objects.

    See Configuring Cloud object retention properties.

    The Advanced restore options are not applicable to the Azure Data Lake workload.

  13. In the Review page, view the summary of all the selections that you made, and click:
    • Start recovery

      Or

    You can see the progress of the restore job in the Activity monitor.