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
Prerequisites for Cloud object store policies
Before you begin creating a policy for a Cloud object store account, consider the following prerequisites.
A valid Cloud object store account to access the bucket(s) and objects.
Keep handy information about the bucket(s) and the criteria that you want to use for selecting objects from them, in the tab.
In the tab, you must have permission to view and select the Cloud object store account(s), and the access host to specify the backup host or scale-out server for a policy.
Evaluate the requirement for NetBackup accelerators in your environment. If you want to use accelerators, you need to specify this while creating the policy.
If you plan to use any other backup host or scale-out server, other than the one used for Cloud object store account validation: Make sure that required ports are opened and configurations are done for communication from the backup host or scale-out server to the cloud provider endpoint using REST API calls.
You can use a scale-out server if you have a large number of buckets in your Cloud object store. NetBackup Snapshot Manager can scale out as many data mover containers as needed at run time, and then scale them down when the data protection jobs are completed. You do not need to worry about configuring multiple backup hosts, and creating multiple policies to distribute the load across these backup hosts.
Evaluate the requirement for NetBackup multistreaming in your environment. For a given bucket, NetBackup creates one stream per query defined for the bucket in the policy. If you want to use multistreaming, you can specify this while creating the policy. To use multistream, you also need to configure the number of jobs for the buckets as client in the section, under primary server Host properties. Add the client name and set the as required.