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
For Azure SQL and SQL Managed Instance
These limitations apply to Azure SQL database and Azure Managed Instance backups using a temporary database.
An Azure VM, which is used as a media server, should be in the same Vnet as that of the Azure-managed instance. Alternatively, if the media server and SQL-managed instance are in different Vnet, then both the Vnets must peer to access the database instance.
Backup fails when Readlock is placed on the database or resource group.
If the databases contain any of these types of tables, the backup fail due to CDC limitations.
Graph tables
Temporal tables
Ledger tables (Updatable ledger)
Memory optimized table (business critical tier only)
For Azure Managed instance databases, if the backup is generated by the native backup database workflow, using TDE enabled by Customer-managed Keys or TDE disabled, these types of tables are supported.
Database diagrams not restored.
NetBackup creates a temporary database in the protected SQL instance using an Azure SQL point-in-time recovery point, to have a read-only and consistent staging database for backup purposes. NetBackup needs additional space on the instance to accommodate the temporary database. The temporary database is of the same size as the protected database.
Backup is partially successful when the Delete lock is placed on the database or resource group.
NetBackup performs cleanup of the temporary databases after backups are complete. If a delete lock is placed on the database or resource group residing on the server, NetBackup cannot delete the temporary database, resulting in a partially successful backup. These stale temporary databases occupy space on the Azure Managed Instance and may result in subsequent backup failures if the instance runs out of space. In such a scenario, manually clean up the temporary database when no NetBackup backup jobs are running for this instance.
To restore a database on an Azure SQL server or Azure Managed Instance, you must assign AAD admin privilege on the target server. Before the restore, assign the rights to any of these:
The system or the user-managed identity of the media servers.
The
vm-scale-setin which the NetBackup media is deployed; in case of AKS or EKS deployment.