For Azure SQL Server and SQL Managed Instance incremental backup
Set the retention period of CDC cleanup jobs to match the incremental schedule and keep them until the next full backup. Otherwise, subsequent backups revert to full.
You may encounter backup or restore issues for databases with encrypted columns in the table. As a workaround, Microsoft suggests using the Publish/Extract commands to tackle this issue.
Restoration may fail for a database with blob data in the table.
To duplicate incremental backups on different storage servers, NetBackup generates different copy numbers for the same recovery point. If you try to restore an incremental copy where no earlier reference of a full or other incremental backup is present, the restore fails.
Note:
Incremental backups of Azure SQL Server can run only on NetBackup media server version 10.2 and higher. Incremental backups of Azure SQL Managed Instances can run only on NetBackup media server version 10.3 and above.
Avoid backing up databases with BLOB data tables. If a table contains BLOB data, then the backup might be successful, but the restore fails.
Encryption setting of an Azure SQL Server or Azure SQL Managed Instance database may not be preserved (Is_encryption=0) during a restore.