{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/", "slug": "dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points", "url": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/" }, "title": "Do not expect new SQL snapshot retention categories to relabel older points", "summary": "Does adding a weekly or monthly category to a SQL instance snapshot policy apply that category to existing recovery points?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:22:46+00:00", "modified_at": "2026-09-10T02:11:19+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 255, "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.", "primary_source": { "name": "Manage and monitor SQL Server database and instance snapshot (preview) on an Azure VM - Azure Backup | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/backup/manage-monitor-sql-database-backup", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Manage and monitor SQL Server database and instance snapshot (preview) on an Azure VM.

", "content_text": "Source facts\nIn 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.\nApplicability\nKeep 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.\nDSE recommendation\nSeparate 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.\nVerification\nIn 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.\nOfficial references\nMicrosoft Learn: Manage and monitor SQL Server database and instance snapshot (preview) on an Azure VM.", "content_markdown": "## Source facts\n\nIn 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).\n\n## Applicability\n\nKeep 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.\n\n## DSE recommendation\n\nSeparate 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.\n\n## Verification\n\nIn 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.\n\n## Official references\n\n[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)." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/", "url": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Do not expect new SQL snapshot retention categories to relabel older points", "item": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/", "url": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/", "headline": "Do not expect new SQL snapshot retention categories to relabel older points", "description": "Does adding a weekly or monthly category to a SQL instance snapshot policy apply that category to existing recovery points?", "abstract": "Does adding a weekly or monthly category to a SQL instance snapshot policy apply that category to existing recovery points?", "articleBody": "Source facts\nIn 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.\nApplicability\nKeep 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.\nDSE recommendation\nSeparate 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.\nVerification\nIn 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.\nOfficial references\nMicrosoft Learn: Manage and monitor SQL Server database and instance snapshot (preview) on an Azure VM.", "datePublished": "2026-09-10T00:22:46+00:00", "dateModified": "2026-09-10T02:11:19+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-550-do-not-expect-new-sql-snapshot-retention-categories-to-relabel-older-points/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Do not expect new SQL snapshot retention categories to relabel older points" }, "articleSection": [ "Business Continuity", "Networks & Infrastructure" ], "keywords": [ "Business Continuity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 255, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Manage and monitor SQL Server database and instance snapshot (preview) on an Azure VM - Azure Backup | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/backup/manage-monitor-sql-database-backup" } } ] } }