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
Recovering RDS-based PaaS asset
You can restore the RDS-based PaaS assets from the tab, under the workload.
To restore RDS-based PaaS assets:
- On the left, click Workloads > Cloud and click the Applications tab. Click the name of the asset that you want to recover.
- Click the Recovery points tab in the calendar, select the date for which you want to see the recovery points.
The available recovery points are displayed on the right.
- Click Recover in the row of the image that you want to recover.
- Under Source databases, select the databases that you want to restore. Click Add database, in the Add database dialog, select the required databases, and click Select.
- (For Amazon RDS Oracle databases only) Enter the staging path in the AWS S3 bucket name field. Click Start recovery. The recovered database appears in the Instant access databases tab. Recovery is possible on self-managed instance EC2 or on-premises VM To complete the recovery of the asset, see the Knowledge base article:
https://www.veritas.com/support/en_US/article.100058945
You can select a different S3 bucket to stage the restored data, than the one used during the backup. You can also select a S3 bucket at a different region.
- Enter a prefix to add to the restored databases, or use the default. This field must have a value.
- (Optional) In the Target instance field, the source instance of the asset is selected by default. To restore to an alternate instance, select the required instance.
- (Optional, for MySQL databases only.) Select Restore metadata to restore metadata such as views, triggers, store procedures, and so on.
- (Optional, for MySQL databases only.) For the target instance credentials for restore:
Select Use already associated credentials to use the credentials that are already associated with the instance, and click Start recovery.
Select Use different credentials to use a different set of credentials, either existing credentials or create a new one.
See Add credentials to a database .
(Optional) Select Make default credentials to set these credentials as default credentials for the asset.
Select a validation host to validate the provided credentials.
- Click Start recovery.
The tab shows you the status.
These two restore workflows implicitly create an instant access mount share against the recovery point.