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 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 target domain.
Creating second account on Cloudian fails by selecting existing region
Explanation:
After adding a Cloud object storage account for Cloudian by adding region with us-east-1 location constraint. If you try to reuse the same region and create a second account, account creation fails.
This happens because region listing API is converting region's location constraint 'us-east-1' to ''<blank> while showing in web UI. You can see added region location constraint was us-east-1 and one which is listed has blank location constraint field. Account created by selecting such region from list fails.
Workaround:
Use the NetBackup Asset Query APIs to create account. Example region details part which can be provided in payload:
"s3RegionDetails": [
{ "regionId": "us-east-1",
"regionName": "<region name same as listed from prior account>",
"serviceHost": "<service host same as listed from prior account>"
}
]You can obtain API DOC from schema API:
https://<primary-server-hostname>/netbackup/asset-service/workloads/saas/schemas/create-or-update-assets-named-query-request