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 parameters for Cloud object store
- Permissions required for Amazon S3 cloud provider user
- Permissions required for Azure blob 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 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 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
Accelerator notes and requirements
Note the following about the NetBackup accelerator:
NetBackup accelerator must be properly licensed. For the latest information on licensing, contact your NetBackup sales or partner representative.
Supports the disk storage units only. Supported storage includes Media Server Deduplication Pool, NetBackup appliance, cloud storage, and qualified third-party OST storage. For supported storage types, see the NetBackup Enterprise Server and Server - Hardware and Cloud Storage Compatibility List at the following URL: http://www.netbackup.com/compatibility
Storage unit groups are supported only if the storage unit selection in the group is Failover.
Supports full backups and incremental backups.
For every policy that enables the Use Accelerator option, the following backup schedules are recommended at a minimum: A full backup schedule with the Accelerator forced rescan option enabled. Another full backup schedule without the Accelerator forced rescan option enabled. See Accelerator force rescan for Cloud object store (schedule attribute).
If a previous backup of the policy, bucket and query does not exist on the backup host or scale-out server, NetBackup performs a full backup, and creates a track log on the backup host or scale-out server. This initial backup occurs at the speed of a normal (not accelerated) full backup. Subsequent Accelerator backups using the same backup host or scale-out server use the track log for accelerated backup speed.
Note:
When you first enable a policy to use accelerator, the next backup (whether full or incremental) is in effect a full backup. It backs up all objects corresponding to Cloud objects queries. If that backup was scheduled as an incremental, it may not be completed within the backup window.
NetBackup retains track logs for future accelerator backups. Whenever you add a query, NetBackup does a full, non-accelerated backup for the queries that are added to the list. The unchanged queries are processed as normal accelerator backups.
If the storage unit that is associated with the policy cannot be validated when you create the policy, it is validated later, when the backup job begins. If accelerator does not support the storage unit, the backup fails. In the bpbrm log, a message appears that is similar to one of the following: Storage server %s, type %s, does not support image include. Storage server type %s, does not support accelerator backup.
Accelerator requires that the storage have the
OptimizedImageattribute enabled.The Expire after copy retention can cause images to expire while the backup runs. To synthesize a new full backup, the SLP-based accelerator backup needs the previous backup.
To detect changes in metadata, NetBackup uses one or more cloud APIs per object/blob. Hence, change detection time increases with the number of objects/blobs to be processed. You may observe backups running longer than expected in cases with little or no data change but a large number of objects.
If in your environment, for a given object, the metadata or tag is always changed (added/removed/updated) with its data. Evaluate using incremental without accelerator over incremental with accelerator from a performance and cost viewpoint.
While creating a Cloud object store policy with multiple tag-based queries, you can use a few simple rules to get the best effect with accelerator. Use the query builder in the policy creation page, and create separate queries, one query per tag. The accelerator-based policies perform best in this configuration.
NetBackup has two ways to determine whether an object is considered for incremental backup or not.
The object's modification time.
Any changes in the tags and user attributes.
These metadata checks are not required for the organization environments where the metadata of the objects do not change after the objects are created. You can use the option in the policy to avoid these metadata checks, which lead to faster change detection and faster accelerated backup.