NetBackup™ Web UI Cloud Object Store Administrator's Guide
- Introduction
- Managing Cloud object store assets
- Protecting Cloud object store assets
- About accelerator support
- About incremental backup
- About policies for Cloud object store assets
- Planning for policies
- Prerequisites for Cloud object store policies
- Creating a backup policy
- Setting up attributes
- Creating schedule attributes for policies
- Configuring the Start window
- Configuring exclude dates
- Configuring include dates
- Configuring the Cloud objects tab
- Adding conditions
- Adding tag conditions
- Example of conditions and tag conditions
- Managing Cloud object store policies
- Recovering Cloud object store assets
- Troubleshooting
- Recovery for Cloud object store using web UI for original bucket recovery option starts but 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 overwrite existing to original location
- Reduced accelerator optimization in Azure for OR query with multiple tags
- Backup is failed and shows a certificate error with Amazon S3 bucket names containing dots (.)
- Azure backup job fails when space is provided in a tag query for either tag key name or value.
- The Cloud object store account has encountered an error
- Bucket list empty when selecting it in policy selection
- Creating second account on Cloudian fails by selecting existing region
- Restore failed with 2825 incomplete restore operation
- Bucket listing of cloud provider fails when adding bucket in Cloud objects tab
- AIR import image restore fails on the target domain if the Cloud store account is not added in 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
Adding a new region
You can add new regions for a specific cloud object store account that you create in NetBackup, while creating the account. When you add a region, access is restricted to the specified region. Region is not available for some Cloud object store providers.
The option to add a new region is not available in the case of Azure Data Lake Storage and Azure Data Lake Storage Government provider types.
To add a region:
- Enter a unique region name. For Location constraint, enter the location identifier that the cloud provider service uses to access the buckets/containers of the associated region. For a public cloud storage, you need to get the location constraint details from the cloud provider.
For the cloud providers that supports AWS v4 signature, specifying the Location constraint field is mandatory. You can obtain the correct value of the location constraint by using the getBucketLocation API on the concerned bucket. If this API returns the location constraint as blank, use 'us-east-1' as the location constraint.
- Enter the service URL. For example:
https://hostname:port_number/service_path - Select the endpoint access style for the cloud service provider. If your cloud service provider additionally supports virtual hosting of URLs, select Virtual Hosted Style, otherwise select Path Style.
- Specify the HTTP and HTTPS ports to use for the region.
- Click Add. The added region appears in the Region table in the Basic properties page.