NetBackup™ for Cloud Object Store Administrator's Guide
- Introduction
- Managing Cloud object store assets
- Planning NetBackup protection for Cloud object store assets
- Enhanced backup performance in 11.0 or later
- Prerequisites for adding Cloud object store accounts
- Configuring buffer size for backups
- Configure a temporary staging location
- Configuring advanced parameters for Cloud object store
- Permissions required for Amazon S3 cloud provider user
- Permissions required for Azure blob storage
- Permissions required for GCP
- Limitations and considerations
- Adding Cloud object store accounts
- Manage Cloud object store accounts
- Scan for malware
- Protecting Cloud object store assets
- About accelerator support
- About incremental backup
- About dynamic multi-streaming
- About storage lifecycle policies
- About policies for Cloud object store assets
- Planning for policies
- Prerequisites for Cloud object store policies
- Creating a backup policy
- Policy attributes
- Creating schedule attributes for policies
- Configuring the Start window
- Configuring the exclude dates
- Configuring the include dates
- Configuring the Cloud objects tab
- Adding conditions
- Adding tag conditions
- Examples of conditions and tag conditions
- Managing Cloud object store policies
- Recovering Cloud object store assets
- Troubleshooting
- Error 5541: Cannot take backup, the specified staging location does not have enough space
- Error 5537: Backup failed: Incorrect read/write permissions are specified for the download staging path.
- Error 5538: Cannot perform backup. Incorrect ownership is specified for the download staging path.
- Reduced acceleration during the first full backup, after upgrade to versions 10.5 and 11.
- After backup, some files in the shm folder and shared memory are not cleaned up.
- After an upgrade to NetBackup version 10.5, copying, activating, and deactivating policies may fail for older policies
- Backup fails with default number of streams with the error: Failed to start NetBackup COSP process.
- Backup fails, after you select a scale out server or Snapshot Manager as a backup host
- Backup fails or becomes partially successful on GCP storage for objects with content encoded as GZIP.
- Recovery for the original bucket recovery option starts, but the 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 overwriting the existing object in the original location
- Reduced accelerator optimization in Azure for OR query with multiple tags
- Backup failed and shows a certificate error with Amazon S3 bucket names containing dots (.)
- Azure backup jobs fail when space is provided in a tag query for either tag key name or value.
- The Cloud object store account has encountered an error
- The bucket is list empty during policy selection
- Creating a second account on Cloudian fails by selecting an existing region
- Restore failed with 2825 incomplete restore operation
- Bucket listing of a cloud provider fails when adding a bucket in the Cloud objects tab
- AIR import image restore fails on the target domain if the Cloud store account is not added to 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 an SLP
The operations in an SLP are the backup instructions for the data. Use the following procedure to create an SLP that contains multiple storage operations.
This section briefly describes SLP creation, for more details see NetBackup™ Administrator's Guide, Volume I.
To create an SLP
- Open the NetBackup web UI.
- On the left, click Storage > Storage lifecycle policies.
- Click Add to create a new SLP.
- On the Storage lifecycle policy pane, provide the following details:
Storage lifecycle policy name: The name cannot be modified after the SLP is created.
Data classification: Defines the level or classification of data that the SLP is allowed to process. The dropdown menu contains all of the defined classifications as well as the Any classification, which is unique to SLPs. The Any selection indicates to the SLP that it should preserve all images that are submitted, regardless of their data classification.
Priority for secondary operations: The priority that jobs from secondary operations have in relationship to all other jobs. The priority applies to the jobs that result from all operations except for Backup and Snapshot operations. Range: 0 (default) to 99999 (highest priority).
For example, you may want to set the Priority for secondary operations for a policy with a gold data classification higher than for a policy with a silver data classification.
- Add one or more operations to the SLP. The operations are the instructions for the SLP to follow and apply to the data that is specified in the backup policy. Click Add to add operations to the SLP. Provide the following on the New operation pane. Select an Operation type.
Source storage > Operation
Select Backup.
Destination storage attributes > Destination storage
Select the required storage.
Retention > Retention type
The Fixed retention indicates that the data on the storage is retained for the specified length of time, after which the backups or snapshots are expired.
Expires immediately, 1 week, 2 weeks, 3 weeks and many more.
An image copy with a fixed retention is eligible for expiration when all of the following criteria are met:
The Fixed retention period for the copy has expired.
All child copies have been created.
All child copies that are mirror copies are eligible for expiration.
The Expire after copy retention indicates that after all direct (child) copies of an image are successfully duplicated to other storage, the data on this storage is expired. The last operation in the SLP cannot use the Expire after copy retention type because no subsequent copy is configured. Therefore, an operation with this retention type must have a child.
The Capacity managed operation means that NetBackup automatically manages the space on the storage, based on the High water mark setting for each volume.
The High water mark and Low water mark settings on the disk storage unit or disk pool determine how the space is managed.
To add a child operation, select an operation and then click Add child. Select an Operation type. For a child operation, the SLP displays only those operations that are valid based on the parent operation that you selected.
- The Window tab displays for the available operation types. Use them to specify when the secondary operation runs, create a window for the operation.
- Optionally, select Postpone creation of this copy until the source copy is about to expire.
- Under Advanced, specify if NetBackup should process active images after the window closes.
- Under Duplication, you can allow an alternate read server to read a backup image originally written by a different media server.