Please enter search query.
Search <book_title>...
NetBackup™ Web UI Cloud Object Store Administrator's Guide
Last Published:
2023-03-31
Product(s):
NetBackup (10.2)
- 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.
Access tier property not restored after overwrite existing to original location
Explanation
Object with access tier Cool, overwritten by a restore with Hot access tier, does not change the access tier to Hot, it remains Cool.
Workaround
In case of Azure cloud storage, when we have an object with accessTier as cool, and we try to upload object/blob of the same name with Hot(inferred) accessTier with overwrite option, accessTier remains as cold. New access tier does not get set. This behavior is observed when file is uploaded from portal. It does not change accessTier from cool to Hot (inferred) when the Overwrite option is selected on Azure portal.