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
- Managing policies for cloud assets
- Limitations and considerations
- Add an SLP and cloud policy
- Operations on cloud policy
- PaaS and IaaS policy SLP configurations
- 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 PaaS assets
- Prerequisites for protecting PaaS assets
- Installing the native client utilities
- Configuring the storage server for instant access
- Prerequisites for protecting Amazon RDS SQL Server database assets
- Configuring storage for different deployments
- 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
- Limitations and considerations
- Discovering PaaS assets
- Viewing PaaS assets
- Managing PaaS credentials
- View the credential name that is applied to a database
- Add credentials to a database
- Add protection to PaaS assets
- Perform backup now
- Protecting AWS or Azure VMs for recovering to VMware
- Cloud asset cleanup
- Cloud asset filtering
- Recovering cloud assets
- Recovering cloud assets
- About the pre-recovery check for VMs
- Supported parameters for restoring cloud assets
- Restoring to a different cloud provider
- Recovering virtual machines
- Recovering applications and volumes to their original location
- Recovering applications and volumes to an alternate location
- Additional steps required after restoring an AWS RDS database instance
- 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
- Restore to a different cloud provider
- 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>
- 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
Configuring incremental backups for Azure MySQL server
NetBackup supports both full and differential incremental backup schedules for Azure MySQL server. During full backup, NetBackup takes a logical dump of all user databases. During incremental backups, NetBackup downloads the binary logs generated on the MySQL server between subsequent incremental backups. When you restore a database, NetBackup creates the database with the full backups and then applies the binary logs in chronological sequence.
Configure the following parameters in the Azure portal.
Table: Parameters for incremental backup
Parameter | Description | Recommendation |
|---|---|---|
| Number of seconds to wait before the binary log file is purged. | This value must be higher than the frequency of backups in the schedule. Ensures that the binary logs on the server are not purged between subsequent incremental backups. |
| The status of binary logging on the server, either enabled (ON) or disabled (OFF). | For incremental backups, this parameter must be set to ON. It captures the changes in the binary log file. |
| This variable applies when binary logging is enabled. It allows the stored function creators to be trusted to make stored functions that allow unsafe events to be written to the binary log. | To restore databases to servers, set this parameter as ON. |
| Specifies the default encryption setting to use for the schemas and general tablespaces, when they are created without specifying an ENCRYPTION clause. | To restore databases to servers, set this parameter as ON. |
| If a transaction requires more memory than this specified value, the server generates a storage error. | Ensure that this value can accommodate the maximum total size of a transaction. We recommend keeping the default value of this parameter. |