NetBackup™ for Cloud Object Store Administrator's Guide
- Introduction
- Managing Cloud object store assets
- Planning NetBackup protection for Cloud object store assets
- Enhanced backup performance in 11.0 or later
- Prerequisites for adding Cloud object store accounts
- Configuring buffer size for backups
- Configure a temporary staging location
- Configuring advanced dynamic multi-streaming parameters
- Permissions required for Amazon S3 cloud provider user
- Permissions required for Azure blob storage
- Permission required for Azure Data Lake Storage
- Permissions required for GCP
- Limitations and considerations
- Adding Cloud object store accounts
- Manage Cloud object store accounts
- Scan for malware
- Protecting Cloud object store assets
- About accelerator support
- About incremental backup
- About dynamic multi-streaming
- About object change tracking
- Configuring object change tracking
- Configuring access permissions for the buckets
- Configuring access policy on the log bucket
- Configuration guidelines for IBM Storage Ceph
- Enable bucket logging for source buckets
- Creating policy for the log bucket
- Additional storage requirements at the staging location
- Configuring bucket logging in IBM Storage Ceph
- Maintaining the log bucket
- Configuring NetBackup for object change tracking
- Configuring NetBackup policy for object change tracking
- Verifying object change tracking in the Activity monitor
- Scenarios when NetBackup overrides object change tracking
- About storage lifecycle policies
- About policies for Cloud object store assets
- Planning for policies
- Prerequisites for Cloud object store policies
- Creating a backup policy
- Policy attributes
- Creating schedule attributes for policies
- Configuring the Start window
- Configuring the exclude dates
- Configuring the include dates
- Configuring the Cloud objects tab
- Adding conditions
- Adding tag conditions
- Examples of conditions and tag conditions
- Managing Cloud object store policies
- Recovering Cloud object store assets
- Troubleshooting
- Error 5549: Cannot validate bucket logging information
- 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.
- Error 5579: Falling back to object listing for change detection, not considering object change tracking for this bucket, specified in the policy.
- Error 5580: The specified failover strategy for the storage unit group is incompatible with the Cloud object store policy, with dynamic multi-streaming.
- Error 5545: Backup failed as NetBackup cannot parse records from the log object
- Error 5541: Cannot take backup, the specified staging location does not have enough space
- Error 5537: Backup failed: Incorrect read/write permissions are specified for the download staging path.
- Error 5538: Cannot perform backup. Incorrect ownership is specified for the download staging path.
- Reduced acceleration during the first full backup, after upgrade to versions 10.5 and 11.
- After backup, some files in the shm folder and shared memory are not cleaned up.
- After an upgrade to NetBackup version 10.5, copying, activating, and deactivating policies may fail for older policies
- Backup fails with default number of streams with the error: Failed to start NetBackup COSP process.
- Backup fails, after you select a scale out server or Snapshot Manager as a backup host
- Backup fails or becomes partially successful on GCP storage for objects with content encoded as GZIP.
- Recovery for the original bucket recovery option starts, but the job fails with error 3601
- Recovery Job does not start
- Restore fails: "Error bpbrm (PID=3899) client restore EXIT STATUS 40: network connection broken"
- Access tier property not restored after overwriting the existing object in the original location
- Reduced accelerator optimization in Azure for OR query with multiple tags
- Backup failed and shows a certificate error with Amazon S3 bucket names containing dots (.)
- Azure backup jobs fail when space is provided in a tag query for either tag key name or value.
- The Cloud object store account has encountered an error
- The bucket is list empty during policy selection
- Creating a second account on Cloudian fails by selecting an existing region
- Restore failed with 2825 incomplete restore operation
- Bucket listing of a cloud provider fails when adding a bucket in the Cloud objects tab
- AIR import image restore fails on the target domain if the Cloud store account is not added to the target domain
- Backup for Azure Data Lake fails when a back-level media server is used with backup host or storage server version 10.3
- Backup fails partially in Azure Data Lake: "Error nbpem (pid=16018) backup of client
- Recovery for Azure Data Lake fails: "This operation is not permitted as the path is too deep"
- Empty directories are not backed up in Azure Data Lake
- Recovery error: "Invalid alternate directory location. You must specify a string with length less than 1025 valid characters"
- Recovery error: "Invalid parameter specified"
- Restore fails: "Cannot perform the COSP operation, skipping the object: [/testdata/FxtZMidEdTK]"
- Cloud store account creation fails with incorrect credentials
- Discovery failures due to improper permissions
- Restore failures due to object lock
Limitations and considerations
Consider the following when protecting Cloud object store workloads.
NetBackup does not allow a prefix or object query that starts with "/". Examples:
prefix = / prefix = /folder1 prefix = /object1 prefix = folder1// object = /obj1
NetBackup does not back up an object with its name in the format:
<name>/
The checkpoint restart feature is not supported with Dynamic multi-streaming.
You can only protect entire buckets with Dynamic multi-streaming.
You must configure backup hosts with at least the minimum recommended staging space.
Upgrading to NetBackup version 11.0:
It is recommended to update the primary server, media server, and backup hosts to the current version.
Upgrade only the primary server: Backup jobs with Dynamic multi-streaming fails. Your must update the backup host used in the policy to the current version.
Upgrade only the primary and media servers: Backup jobs with Dynamic multi-streaming fails. Your must update the backup host used in the policy to the current version.
Upgrade only primary server and backup host and media server remains at an older version: NetBackup protection works.
If you upgrade to the latest NetBackup version from version 10.1 or 10.2, the following limitations occur:
You can create Cloud object store accounts with backup hosts or scale-out servers of version 10.3 or later only. You cannot update an existing Cloud object store account that was created on NetBackup 10.3 or later with backup hosts or scale-out servers older than version 10.3.
You can create policies only with backup hosts or scale-out servers of version 10.3 or later. You cannot update an existing policy that is created on NetBackup 10.3 or later with backup hosts or scale-out servers older than version 10.3.
The following credential types are not supported with backup hosts or scale-out servers older than version 10.3: For Azure: Service principal and Managed identity. For AWS: Assume role (EC2).
Restores with object lock properties are supported for backup hosts or scale-out servers of version 10.3 or later only.
Backup and restore of buckets with default retention enabled are supported with backup hosts or scale-out servers of version 10.3 or later only.
For Azure, if you update a policy created with NetBackup version prior to 10.3, with a backup host or scale-out server of version 10.3 or later, the backups fail. As a workaround, update all the buckets to use the new format of the provided generated ID with the existing queries. Note that you must create the associated Cloud object store account in the policy, using NetBackup 10.3 or later, for this workaround to be successful.
Discovery is supported for NetBackup version 10.3 or later, deployed on RHEL, and NetBackup version 11.0.0.1 or later deployed on RHEL and SUSE. If no supported host is available, then discovery does not start for any of the configured Cloud storage accounts. In this case, discovery status is not available, and you cannot see a bucket list during policy creation. Even if you add the buckets manually after discovery fails, your backups may fail. Upgrade at least one supported backup host or scale-out server and create a new policy.
If you update a policy that is created on a NetBackup version prior to 10.3, consider the following after a backup:
After backup, you may see two versions of the same buckets, for the old and new formats. If you want to restore old data, select the bucket in the old format. For newer backups, select the ones in the newer format.
The subsequent backup after the update is a full backup, irrespective of what is configured in the policy.
When you upgrade to 10.3, the first Azure blob accelerated backup takes a backup of all objects in the selection, even if the configured backup is incremental. This full backup is required for the change in metadata properties for the Azure blobs between NetBackup versions 10.2 and 10.3. The subsequent incremental backups back up only the changed objects.
If you use a Cloud object store account created in a version older than 10.3, NetBackup discovers the buckets with the old format, where: uniqueName=bucketName.