NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- 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
- Configuring the Start window
- Managing cloud policies
- Scan for malware
- Protecting Microsoft Azure resources using resource groups
- NetBackup Accelerator for cloud workloads
- AWS Snapshot replication
- Protecting PaaS assets
- Protecting RDS Custom instances
- Protecting Azure Managed Instance databases
- Limitation and considerations
- Installing the native client utilities
- Configuring storage for different deployments
- Managing PaaS credentials
- Add protection to PaaS assets
- Recovering cloud assets
- Recovering 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 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-set
in which the NetBackup media is deployed; in case of AKS or EKS deployment.