NetBackup™ Web UI Cloud Object Store Administrator's Guide
- Introduction
- Managing Cloud object store assets
- Protecting Cloud object store assets
- About accelerator support
- Managing Cloud object store policies
- Recovering Cloud object store assets
- Troubleshooting
Features of NetBackup Cloud object store workload support
Table: Salient features
Feature |
Description |
---|---|
Integration with NetBackup role-based access control (RBAC) |
The NetBackup web UI provides the Default cloud object store Administrator RBAC role to control which NetBackup users can manage Cloud object store operations in NetBackup. The user does not need to be a NetBackup administrator to manage Cloud object store operations. |
Management of Cloud object store accounts |
You can configure a single NetBackup primary server for multiple Cloud object store accounts, across different cloud vendors as required. |
Authentication and credentials |
Wide emphasis for security. For protecting a single Azure Blob Storage account, Storage account, and Access Key must be specified. To protect Azure blob storage account, the supported authentication mechanisms are Access key, Service Principal, and Managed Identity. For all S3 API-compliant cloud vendors, Access key and Secret Key are supported. For Amazon S3, in addition to Access Key, IAM role, and Assume role (For cross-AWS account) mechanism of authentication are also supported. |
Backup policy |
A single backup policy can protect multiple S3 buckets or Azure blob containers from one Cloud object store account. |
Intelligent selection of cloud objects |
Within a single policy, NetBackup provides flexibility to configure different queries for different buckets or containers. Some buckets or containers can be configured to backup all objects in them. You can also configure some buckets and containers with intelligent queries to identify objects based on:
|
Scalable solution |
In addition to full backup, NetBackup also supports different types of incremental schedules for faster backups. Accelerator feature is also supported for Cloud object store policy. Enable checkpoint restart in the policy to be able to restart a failed or suspended job, right from the point that it stopped. We do not need to repeat the entire data transfer from the start of the job. |
Granular restore |
NetBackup supports an easy way to restore all objects in a bucket/container, as well as provides prefix, folder and object-based views to restore only a selected subset of the objects. You can narrow down a selection of backup images for restore in NetBackup by providing a date and time range. |
Restore options |
NetBackup supports adding an arbitrary prefix to all objects when restoring. Thereby, restores the objects with a different name when you do not want the restored objects to interfere with the original objects. For Azure Data Lake files and directories, however, does not require a prefix. Instead, the files and directories are restored to a specified alternate location. By default, NetBackup skips overwriting objects that already exist in the cloud object store to conserve on bandwidth and cloud costs. You can change this default behavior using the Overwrite option, so that restored copies can overwrite the cloud object store copies. |
Alternate location restores |
Objects selected for restore can be restored:
|
Scale-out support |
NetBackup Cloud object store protection supports configuring NetBackup Snapshot Manager (NBSM) as a backup host in addition to a media server as backup host. With the scale-out server option, you can manage large number of buckets in their Cloud object store. You do not need to configure multiple backup hosts, and creating multiple policies to distribute the load across these backup hosts. 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. |
Object lock |
This feature lets you retain the original object lock properties and also provides an option to customize the object lock properties. When you apply object lock properties on restored objects, the restored objects cannot be deleted until the retention period is over, or the legal holds are removed. No configuration is needed during policy creation and backup to use the object lock and retention properties backup. |