# Export an Elastic SAN snapshot before deleting its source volume

> An in-SAN snapshot shares its source volume's deletion lifecycle; independent retention requires a completed managed-disk snapshot export.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:27:39+00:00
- Modified: 2026-09-10T01:23:48+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

An in-SAN snapshot shares its source volume's deletion lifecycle; independent retention requires a completed managed-disk snapshot export.

## 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.

## Article

## Source facts

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.

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. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-snapshots).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[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.

## Primary reference

- Name: Backup Azure Elastic SAN volumes | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-snapshots
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Export an Elastic SAN snapshot before deleting its source volume,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-257-export-an-elastic-san-snapshot-before-deleting-its-source-volume/
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.