About incremental backup for PaaS workloads
NetBackup supports differential incremental backup for Azure SQL Server, Azure SQL Managed Instance, AWS RDS Oracle, 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, AWS RDS Oracle, 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 the 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. If any of the previous dependent full or incremental images are missing, it may result in failure.
Differential incremental backup is supported on AWS RDS Oracle, only if schema changes are managed by the RDS.