An Azure backup service that provides built-in management at scale.
Hello Torben Strüver,
Thank you for sharing the results from your Azure Backup for PostgreSQL Flexible Server and Elastic Cluster v2 Preview testing.
Kindly note that the behavior you observed can be expected. In v2, the first backup is a full physical backup. Subsequent scheduled backups are incremental and transfer only changed blocks. However, the overall backup job duration is not determined only by the amount of changed data.
Each scheduled backup still includes platform processing steps such as creating and hydrating the managed disk snapshot, obtaining access to the current and previous snapshots, calculating the difference between them, and copying the required data to the Backup vault. The backup job is marked successful only after the required data has been copied to the vault.
Because these fixed workflow steps still run for each scheduled backup, an incremental backup may take approximately the same wall-clock duration as the initial backup, even when daily data changes are minimal. This does not necessarily indicate that the backup is running as a full backup each time.
For your planned approximately 4-TB PostgreSQL Flexible Server, this size is within the documented v2 supported scale limits. The documented limits are up to 32 TB on Premium SSD v1 and up to 64 TB on Premium SSD v2.
Regarding backup-window estimation, We don't have a fixed throughput rate, sizing calculator, formula, or guaranteed duration estimate for calculating the backup duration of a 4-TB PostgreSQL Flexible Server in v2. Since the total job duration can be influenced by storage type, snapshot processing, data churn, vault copy time, and platform activity during the backup window, the supported recommendation is to run representative production-like testing over multiple scheduled backup cycles and use the measured job durations as the baseline for production planning.
In summary, the similar duration between the initial backup and subsequent incremental backups can be expected due to the end-to-end backup workflow overhead. The 4-TB server size is supported in v2, but there is no published formula or guaranteed estimate for the backup window. The recommended planning method is to validate with representative testing and use observed backup job durations across multiple cycles.