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
About dynamic multi-streaming
Multi-streaming backup for Cloud object store policy runs simultaneous backup streams for a given backup selection. The backup selection is divided into several streams that run in parallel, resulting in a faster backup. The number of streams can be configured for each policy in the backup selection tab of the cloud object store policy. Each backup stream creates a unique backup image. Eventually, all the images created by the streams for that backup selection represent the backup of that specific selection.
Dynamic muti-streaming is enabled by default on all newly created Cloud object store policies.
You can specify the maximum number of streams that you want to use for a bucket or container in the policy attributes.
See Policy attributes.
Entire buckets/containers are backed up when you use dynamic multi-streaming.
The number of streams that you specify in a policy is applicable for each of the buckets that the policy protects. For example, if you specify 10 streams in the policy and select five buckets for backup, you get 50 concurrent streams. Some streams may go to a queue, if the maximum number of concurrent jobs allowed in the storage unit selected for the policy, is less than the total number of streams that are running across different policies. For optimal performance, keep the allowed property of selected storage greater than the total number of streams that you expect to run across the policies.
You cannot use a scale-out server as a backup host, when you use dynamic multi-streaming.
Dynamic multi-streaming requires staging location path.
Job retry feature does not work for backup jobs.
Dynamic multi-streaming is not available for Azure Data Lake storage and Azure Data Lake storage Government providers.
Checkpoint restart is not supported.
You must configure a temporary staging location as per guidelines to use this feature. See Configure a temporary staging location.
Dynamic multi-streaming starts all the backup streams for a bucket or container at the same time and writes to a storage unit. Therefore, using tape storage units as the target for primary backup copies is not recommended. You can use an MSDP storage as the target for the first backup copy, and configure a tape storage as the target for secondary or duplication copies.