Search <book_title>...

NetBackup™ Web UI Cloud Object Store Administrator's Guide

Last Published: 2024-03-27

Product(s): NetBackup & Alta Data Protection (10.4)

Limitations and considerations

Consider the following when protecting Cloud object store workloads.

Limitations based on the upgrade scenario

If you upgrade to NetBackup version 10.3, from versions 10.1 or 10.2, the following limitations apply.
- 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 supported with backup hosts or scale-out servers older than version 10.3 only: 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. 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 an Azure blob has the Content Encoding property assigned as "gzip" or "x-gzip", NetBackup does not download that blob and backup. The backup job is marked as partially done. You can see the following message in the activity monitor:
Error bpbrm (pid=XXX) from client XYZ_CLIENT: ERR - File /ABC.zzz shrunk by <size> bytes, padding with zeros.
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.
NetBackup does not allow the following combinations as part of a prefix or object query:
```
prefix = /
prefix = /folder1
prefix = /object1
prefix = folder1//
object = /obj1
```