# Do not expect new SQL snapshot retention categories to relabel older points

> Does adding a weekly or monthly category to a SQL instance snapshot policy apply that category to existing recovery points?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:22:46+00:00
- Modified: 2026-09-10T02:11:19+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

Does adding a weekly or monthly category to a SQL instance snapshot policy apply that category to existing recovery points?

## Potentially affected

Keep this decision specific to SQL Server instance snapshot backup, which the source labels preview. Identify the current policy, proposed category and recovery points whose treatment matters; do not substitute the streaming-database policy procedure.

## DSE recommendation

Separate a retention-duration edit from adding a new retention category in the change assessment.

## Article

## Source facts

In Azure Backup’s SQL Server instance snapshot preview, a retention-setting change applies to existing and future recovery points. However, a weekly, monthly or yearly retention category newly added to an existing policy applies only to future points. Microsoft documents policy management through the Recovery Services vault and says SQL instance snapshot backup management is not supported in Resiliency. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/backup/manage-monitor-sql-database-backup).

## Applicability

Keep this decision specific to SQL Server instance snapshot backup, which the source labels preview. Identify the current policy, proposed category and recovery points whose treatment matters; do not substitute the streaming-database policy procedure.

## DSE recommendation

Separate a retention-duration edit from adding a new retention category in the change assessment. Ask the backup owner to state which existing points the change is expected to affect. Compare that expectation with the category boundary before approving a revised policy. If an older point is needed for a recovery obligation, confirm its actual retained status rather than assuming the newly added schedule will cover it. Preserve the original policy and recovery-point inventory for comparison.

## Verification

In an approved preview evaluation, record representative existing points before the edit and inspect them afterward. Separately examine points created after the new category takes effect. Compare observed retention with the documented distinction and the approved recovery requirement. Escalate any mismatch before treating the revised policy as evidence of historical coverage; do not delete older recovery data as part of this test.

## Official references

[Microsoft Learn: Manage and monitor SQL Server database and instance snapshot (preview) on an Azure VM](https://learn.microsoft.com/en-us/azure/backup/manage-monitor-sql-database-backup).

## Primary reference

- Name: Manage and monitor SQL Server database and instance snapshot (preview) on an Azure VM - Azure Backup | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/backup/manage-monitor-sql-database-backup
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Do not expect new SQL snapshot retention categories to relabel older points,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.