An Azure backup service that provides built-in management at scale.
Hello Jonathan Potthast,
Thank you for reaching out to the Microsoft Q&A forum.
When investigated we see that what happened is exactly how the long-term retention (LTR) policies work today:
- When you reduced your “Weekly backup retention” from 52 to 12 weeks, any backups older than 12 weeks were immediately marked as expired and purged.
- The “Monthly backup retention” setting in LTR always keeps only the first full backup of each month (up to your specified number of months). It does not automatically pick one of the weekly backups taken later in the month. Because you didn’t have a full backup taken at the start of each month under the new policy, there was nothing for it to retain.
Unfortunately, once an LTR backup passes its expiration date it’s permanently deleted and can’t be restored. You’ll only be able to recover data from backups that are still within your 12-week (weekly) or 36-month (monthly, first-of-month) window.
To avoid this in the future, a common pattern is:
• Set Monthly retention before you shorten Weekly retention • Make sure you let at least one full backup occur right after the first of the month (so the monthly policy has a “first-of-month” backup to retain) • Then safely reduce your weekly window without losing your monthlies
Hope that clears it up!
Reference docs:
• Manage long-term backup retention for your database https://docs.microsoft.com/azure/sql-database/sql-database-long-term-backup-retention?WT.mc_id=pid:13491:sid:32630432
• Configure weekly/monthly LTR policies https://docs.microsoft.com/azure/azure-sql/database/long-term-backup-retention-configure?WT.mc_id=pid:13491:sid:32630432/
• LTR settings explained (W/M/Y/WeekOfYear) https://docs.microsoft.com/azure/backup/backup-azure-backup-cloud-as-tape?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#what-is-the-retention-policy