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.
About incremental backup
NetBackup supports incremental backup for Cloud object store workloads. You can use incremental backup without enabling accelerator.
For Cloud object store workload, there are some metadata properties that do not alter the modification time for an object or blob. For example, the Tags in Azure blobs. Even if you change these metadata properties, the corresponding objects are not considered for the next incremental backup. This may appear like loss of data during incremental backup.
For detailed list of metadata properties that do not alter modification time for an object or blob, refer to the respective cloud provider's documentation.
For incremental backups, if an object name has path style naming scheme, then for each path, an entry is added in NetBackup. If the object, which is represented by the end node of this path style naming, has not changed since last backup (either full or last incremental, based on incremental schedule used), then that object is not included in the next incremental backup. Because of this behavior, empty paths show up in the catalog and are rendered in the browse view of restore.