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 Azure-protected assets
NetBackup lets you restore Azure SQL database and Azure SQL managed database assets that are backed up by Microsoft Azure. The supported backup modes are Point-in-time backup and Long-term retention backup.
Note:
Restoration in Elastic pool in Instance pool is not supported.
Before proceeding make sure that you have the required permissions to restore PaaS assets.
To recover point-in-time backup assets:
- On the left, click Workload > Cloud.
- Click the PaaS tab.
All the discovered PaaS assets are displayed.
- Under Recovery points type, select Provider protected.
- Click Restore in the row of the protected Azure SQL database and Azure SQL managed database asset that you want to recover.
- In the Recovery points tab, under Point in time backup, click Restore.
- Select a date and time under Restore point (UTC). You can select any restore point, between the earliest restore point, and the:
Latest backup time for online databases.
Database deletion time for deleted databases.
Microsoft Azure may round off the selected time to the nearest available recovery point, using UTC.
The default restore date and time displayed in web UI may differ based on the selected PaaS asset. For example, for Azure SQL databases, the default restore time is the current time, and for Azure SQL managed databases, the default restore time is 6 minutes earlier than the current time.
- Optionally, for Azure SQL databases, enter a name for the restored database in the Database name field. Database names cannot have special characters like < > * % & : \ / and ? or control characters. Do not end the name with a period or space. For more information about Azure resource naming rules, see https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftsql
If you do not enter a name, NetBackup automatically assigns a name in the <dbName>_<Restored time in UTC> format.
- Optionally, for Azure SQL managed databases, enter the instance name in the Managed instance field. By default, the instance name of the recovery point is displayed. You can also search for the managed instance name using the search option. You can restore to the same region to which your subscription belongs.
If you cannot see the desired managed instance in the search results, perform a manual discovery. Also, ensure that you have RBAC access to the managed instance.
- Click Next. Once the Pre-recovery check is complete, click Start recovery.
You can check the status of the job in the activity monitor.
To recover long-term retention backup assets:
- On the left, click Workloads > Cloud.
- Click the PaaS tab.
All the discovered PaaS assets are displayed.
- Click Restore in the row of the protected asset that you want to recover.
- In the Recovery points tab, under Long term retention backup, click Restore against the image that you want to restore.
- Optionally, for Azure SQL databases, enter a name for the restored database in the Database name field. Database names cannot have special characters like < > * %& : \ / and ? or control characters. Do not end the name with a period or space. For more information about Azure resource naming rules, see https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftsql
If you do not enter a name, NetBackup automatically assigns a name in the restore_<dbName> format.
- Optionally, for Azure SQL managed databases, enter the instance name in the Managed instance field. By default, the instance name of the recovery point is displayed. You can also search for the managed instance name using the search option. You can restore to the same region to which your subscription belongs.
- Click Next. Once the Pre-recovery check is complete, click Start recovery.
You can check the status of the job in the activity monitor.
Note:
Tags from the portal as well as Snapshot Manager are not restored. However, the "createdby: cloudpoint" tag is created while restoring through NetBackup.
Note:
For provider-protected recovery jobs, any intermittent failures keep the recovery job running until the next schedule job cleanup runs.