NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- AWS and Azure government cloud support
- Configure Snapshot Manager in NetBackup
- Managing intelligent groups for cloud assets
- Protecting cloud assets or intelligent groups for cloud assets
- About storage lifecycle policies
- Managing policies for cloud assets
- Limitations and considerations
- Planning for policies
- Creating policies for cloud assets
- Setting up attributes for PaaS assets
- Setting up attributes for IaaS assets
- Creating schedules
- About backup frequency
- About assigning retention periods
- Configuring the Start window
- Configuring the include dates
- Configuring the exclude dates
- Configuring the cloud assets for PaaS
- Configuring the cloud assets for IaaS
- Configuring backup options for IaaS
- Managing cloud policies
- Scan for malware
- Protecting Microsoft Azure resources using resource groups
- NetBackup Accelerator for cloud workloads
- Configuring backup schedules for cloud workloads using protection plan
- Backup options for cloud workloads
- AWS Snapshot replication
- Protect applications in-cloud with application-consistent snapshots
- Protecting AWS or Azure VMs for recovering to VMware
- Cloud asset cleanup
- Cloud asset filtering
- Protecting PaaS assets
- Protecting PaaS assets
- Prerequisites for protecting PaaS assets
- Enabling binary logging for MySQL and MariaDB databases
- Enabling backup and restore in Kubernetes
- Prerequisites for protecting Amazon RDS SQL Server database assets
- Protecting RDS Custom instances
- Protecting Azure Managed Instance databases
- Limitation and considerations
- For all databases
- For PostgreSQL
- For incremental backups for Azure PostgreSQL
- For AWS RDS PostgreSQL and AWS Aurora PostgreSQL
- For AWS DynamoDB
- For AWS DocumentDB
- For AWS Neptune
- For AWS RDS SQL
- For Azure, AWS RDS, and Aurora MySQL
- For incremental backups using Azure MySQL server
- For incremental backups using the GCP SQL Server
- For Azure SQL and SQL Managed Instance
- For Azure SQL and SQL Managed Instance (without temp. database)
- For Azure SQL Server and SQL Managed Instance incremental backup
- For Azure Cosmos DB for MongoDB
- For Azure Cosmos DB for NoSQL
- For Amazon RDS for Oracle
- For Amazon Redshift databases
- For Amazon Redshift clusters
- For GCP SQL Server
- For GCP BigQuery
- Installing the native client utilities
- Configuring storage for different deployments
- Configuring the storage server for instant access
- About incremental backup for PaaS workloads
- Configuring incremental backups for Azure MySQL server
- About archive redo log backup for PaaS workloads
- About Auto Image Replication for PaaS workloads
- Discovering PaaS assets
- Viewing PaaS assets
- Managing PaaS credentials
- Add protection to PaaS assets
- Recovering cloud assets
- Recovering cloud assets
- About the pre-recovery check for VMs
- Supported parameters for restoring cloud assets
- Recovering virtual machines
- Recovering applications and volumes to their original location
- Recovering applications and volumes to an alternate location
- Recovery scenarios for GCP VMs with read-only volumes
- (GCP only) Restoring virtual machines and volumes using the autoDelete disk support
- Perform rollback recovery of cloud assets
- Recovering AWS or Azure VMs to VMware
- Recovering PaaS assets
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
- Troubleshoot cloud workload protection issues
- Error Code 9855: Error occurred while exporting snapshot for the asset: <asset_name>
- VMs and other OCI assets with CMK-encrypted disks are marked as deleted in NetBackup UI.
- Backup from snapshot jobs take longer time than expected
- Backup from snapshot job fails due to connectivity issues when Snapshot Manager is deployed on an Ubuntu host
- Error disambiguation in NetBackup UI
- Status Code 150: Termination requested by administrator
- Troubleshoot PaaS workload protection and recovery issues
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.
For SLP best practices, see the Knowledge Article: https://www.veritas.com/content/support/en_US/article.100009913.
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
Backup
Snapshot
Import
Destination storage attributes > Destination storage
Snapshot
No storage unit
Snapshot
Destination storage attributes > Volume pool
NetBackup
Note:
For Snapshot and Import operation, this option is disabled.
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.
To understand the different SLP configurations for various snapshot and backup operations: