NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- Configure Snapshot Manager in NetBackup
- Managing intelligent cloud groups
- Protecting cloud assets or intelligent cloud groups
- Cloud asset cleanup
- Cloud asset filtering
- AWS and Azure government cloud support
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Configuring backup schedule for cloud workloads
- Backup options for cloud workloads
- Snapshot replication
- Configure AWS snapshot replication
- Using AWS snapshot replication
- Support matrix for account 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
- Configuring storage for different deployments
- About incremental backup 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
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
About incremental backup for PaaS workloads
NetBackup supports differential incremental backup for Azure SQL Server, Azure SQL Managed Instance, and GCP SQL Server workloads. Incremental backups reduce the backup window significantly in NetBackup. In this method, NetBackup, backs up only the data that has been changed since the subsequent full backup.
Differential incremental backup is only supported for those workloads, where the Change Data Capture feature on the Azure SQL Server, GCP SQL Server, and Azure SQL Managed Instance are enabled.
Guidelines for working with incremental backups for PaaS workloads:
Assign a longer retention period to full backups than to incremental backups within a policy. A complete restore requires the previous full backup plus all subsequent incremental backups. It may not be possible to restore all the files if the full backup expires before the incremental backups.
Use one storage for full and incremental backups.
Do not create long-term copy for incremental backups.
Do not expire random incremental backup images. Expiring them may cause application inconsistency due to data loss. NetBackup relies on previous full backup and all the subsequent incremental backups.
While duplicating, ensure that the full and the incremental backup copies are duplicated to the target storage. Any of the previous full or incremental images missing may result in data loss.
While importing, ensure that the full and all the incremental backup copies are imported together. Any of the previous dependent full or incremental images missing may result in failure.