[DEV-15000] Update Azure postgres clusters to use differential backups instead of incremental.

[NathanOkolita]

Note

Medium Risk
Changes the backup strategy and schedule for Azure Postgres clusters, which can affect restore behavior, storage usage, and backup/restore timelines if misconfigured.

Overview
Updates azure/application.tf to stop scheduling pgBackRest incremental backups and instead run daily differential backups at midnight for both repo1 (primary Postgres) and repo2 (insights Postgres). The weekly full backup schedule is unchanged.

^{Written by Cursor Bugbot for commit 8bd5bfc. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Backup frequency silently reduced from hourly to daily
  • Restored the postgres-insights differential backup cron from daily (0 0 * * *) to hourly (0 */1 * * *) so only the backup type changed.

Or push these changes by commenting:

@cursor push 473215fc03

Preview (473215fc03)

diff --git a/azure/application.tf b/azure/application.tf
--- a/azure/application.tf
+++ b/azure/application.tf
@@ -678,7 +678,7 @@
         container: " ${module.storage.crunchy_backup_name}"
       schedules:
         full: 30 4 * * *
-        differential: 0 0 * * * # Diff backup daily at midnight
+        differential: 0 */1 * * * # Diff backup hourly
     jobs:
       resources:
         requests:

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

[cursor]

Backup frequency silently reduced from hourly to daily

High Severity

The postgres-insights cluster's backup schedule was changed from hourly (0 */1 * * *) to daily (0 0 * * *) when switching from incremental to differential. The first cluster (postgres-data) correctly preserved its original daily schedule during the type change, but this second cluster's cron expression appears to have been copy-pasted from the first, silently reducing backup frequency from 24×/day to 1×/day. This significantly increases the recovery point objective (RPO) for the insights database.