{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/",
        "slug": "dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/"
        },
        "title": "Export an Elastic SAN snapshot before deleting its source volume",
        "summary": "An in-SAN snapshot shares its source volume's deletion lifecycle; independent retention requires a completed managed-disk snapshot export.",
        "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": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "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:27:39+00:00",
        "modified_at": "2026-09-10T01:23:48+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 250,
        "potentially_affected": "Azure Elastic SAN volume snapshots that must be retained independently of their source volume.",
        "dse_recommendation": "Verify the managed-disk snapshot export and recovery path before authorizing source-volume deletion.",
        "primary_source": {
            "name": "Backup Azure Elastic SAN volumes | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-snapshots",
            "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": "<h2>Source facts</h2>\n<p>Deleting an Elastic SAN source volume automatically deletes its Elastic SAN snapshots. Microsoft directs users who need independent retention to export a volume snapshot as a managed disk snapshot, monitoring CompletionPercentage for progress.</p>\n<p>The first snapshot after a volume resize is not incremental and its export can fail. A snapshot can create a new volume, but cannot roll an existing volume back in place. <a href=\"https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-snapshots\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Identify the source volume, selected recovery point, resize history and retention requirement. Elastic SAN snapshot export is same-region only; creating an Elastic SAN volume from a managed disk snapshot also requires both resources in the same region. Distinguish keeping an in-SAN snapshot from holding an independent exported artifact before planning any deletion.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends making export verification a prerequisite in the volume-retirement approval. Record the destination snapshot identity, observed completion and a tested recovery method. Do not assume an export request or visible destination object proves the data is ready. Resolve a failed post-resize export before proceeding, and keep destructive work outside the verification exercise until evidence supports the decision.</p>\n<h2>Verification</h2>\n<p>In an approved nonproduction recovery test, inspect export completion and use the resulting snapshot to create the intended recovery target. Validate representative data and application requirements, including consistency expectations. Compare the result with the selected recovery point and retain any gaps. Authorize deletion only through the separate retirement process after confirming the required independent retention evidence.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-snapshots\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Backup Azure Elastic SAN volumes</a>. Source retrieved September 9, 2026.</p>",
        "content_text": "Source facts\nDeleting an Elastic SAN source volume automatically deletes its Elastic SAN snapshots. Microsoft directs users who need independent retention to export a volume snapshot as a managed disk snapshot, monitoring CompletionPercentage for progress.\nThe first snapshot after a volume resize is not incremental and its export can fail. A snapshot can create a new volume, but cannot roll an existing volume back in place. Microsoft Learn.\nApplicability\nIdentify the source volume, selected recovery point, resize history and retention requirement. Elastic SAN snapshot export is same-region only; creating an Elastic SAN volume from a managed disk snapshot also requires both resources in the same region. Distinguish keeping an in-SAN snapshot from holding an independent exported artifact before planning any deletion.\nDSE recommendation\nDSE recommends making export verification a prerequisite in the volume-retirement approval. Record the destination snapshot identity, observed completion and a tested recovery method. Do not assume an export request or visible destination object proves the data is ready. Resolve a failed post-resize export before proceeding, and keep destructive work outside the verification exercise until evidence supports the decision.\nVerification\nIn an approved nonproduction recovery test, inspect export completion and use the resulting snapshot to create the intended recovery target. Validate representative data and application requirements, including consistency expectations. Compare the result with the selected recovery point and retain any gaps. Authorize deletion only through the separate retirement process after confirming the required independent retention evidence.\nOfficial references\nMicrosoft Learn: Backup Azure Elastic SAN volumes. Source retrieved September 9, 2026.",
        "content_markdown": "## Source facts\n\nDeleting an Elastic SAN source volume automatically deletes its Elastic SAN snapshots. Microsoft directs users who need independent retention to export a volume snapshot as a managed disk snapshot, monitoring CompletionPercentage for progress.\n\nThe first snapshot after a volume resize is not incremental and its export can fail. A snapshot can create a new volume, but cannot roll an existing volume back in place. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-snapshots).\n\n## Applicability\n\nIdentify the source volume, selected recovery point, resize history and retention requirement. Elastic SAN snapshot export is same-region only; creating an Elastic SAN volume from a managed disk snapshot also requires both resources in the same region. Distinguish keeping an in-SAN snapshot from holding an independent exported artifact before planning any deletion.\n\n## DSE recommendation\n\nDSE recommends making export verification a prerequisite in the volume-retirement approval. Record the destination snapshot identity, observed completion and a tested recovery method. Do not assume an export request or visible destination object proves the data is ready. Resolve a failed post-resize export before proceeding, and keep destructive work outside the verification exercise until evidence supports the decision.\n\n## Verification\n\nIn an approved nonproduction recovery test, inspect export completion and use the resulting snapshot to create the intended recovery target. Validate representative data and application requirements, including consistency expectations. Compare the result with the selected recovery point and retain any gaps. Authorize deletion only through the separate retirement process after confirming the required independent retention evidence.\n\n## Official references\n\n[Microsoft Learn: Backup Azure Elastic SAN volumes](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-snapshots). Source retrieved September 9, 2026."
    },
    "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-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Export an Elastic SAN snapshot before deleting its source volume",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/",
                "headline": "Export an Elastic SAN snapshot before deleting its source volume",
                "description": "An in-SAN snapshot shares its source volume's deletion lifecycle; independent retention requires a completed managed-disk snapshot export.",
                "abstract": "An in-SAN snapshot shares its source volume's deletion lifecycle; independent retention requires a completed managed-disk snapshot export.",
                "articleBody": "Source facts\nDeleting an Elastic SAN source volume automatically deletes its Elastic SAN snapshots. Microsoft directs users who need independent retention to export a volume snapshot as a managed disk snapshot, monitoring CompletionPercentage for progress.\nThe first snapshot after a volume resize is not incremental and its export can fail. A snapshot can create a new volume, but cannot roll an existing volume back in place. Microsoft Learn.\nApplicability\nIdentify the source volume, selected recovery point, resize history and retention requirement. Elastic SAN snapshot export is same-region only; creating an Elastic SAN volume from a managed disk snapshot also requires both resources in the same region. Distinguish keeping an in-SAN snapshot from holding an independent exported artifact before planning any deletion.\nDSE recommendation\nDSE recommends making export verification a prerequisite in the volume-retirement approval. Record the destination snapshot identity, observed completion and a tested recovery method. Do not assume an export request or visible destination object proves the data is ready. Resolve a failed post-resize export before proceeding, and keep destructive work outside the verification exercise until evidence supports the decision.\nVerification\nIn an approved nonproduction recovery test, inspect export completion and use the resulting snapshot to create the intended recovery target. Validate representative data and application requirements, including consistency expectations. Compare the result with the selected recovery point and retain any gaps. Authorize deletion only through the separate retirement process after confirming the required independent retention evidence.\nOfficial references\nMicrosoft Learn: Backup Azure Elastic SAN volumes. Source retrieved September 9, 2026.",
                "datePublished": "2026-09-10T00:27:39+00:00",
                "dateModified": "2026-09-10T01:23:48+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/"
                },
                "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-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/#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": "Export an Elastic SAN snapshot before deleting its source volume"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 250,
                "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": "Backup Azure Elastic SAN volumes | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-snapshots"
                }
            }
        ]
    }
}