# Wait for ordered snapshot copies to finish before accepting a regional recovery copy

> When is a managed cross-region incremental snapshot copy ready for restoration?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:31:07+00:00
- Modified: 2026-09-10T00:32:01+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Checklist
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

When is a managed cross-region incremental snapshot copy ready for restoration?

## Potentially affected

Operators copying Azure managed-disk incremental snapshots between regions using the managed copy process.

## DSE recommendation

Track each disk's snapshot sequence and retain its source until the target copy reaches the documented completion state.

## Article

## Source facts

Microsoft’s managed cross-region process copies changes since the previous snapshot in the target region. For a particular disk, only one incremental snapshot can be copied at a time, and copies must follow creation order. The source snapshot must not be deleted during copying. The target’s CompletionPercent must reach 100 before it can restore a disk or provide a SAS download URI. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-copy-incremental-snapshot-across-regions).

## Applicability

Apply this review to the managed incremental-snapshot copy workflow, not a full snapshot or a separately implemented block-difference copier. Identify the disk, source snapshots, target region, and intended recovery point before scheduling the sequence. Keep the copy’s completion criteria separate from application recovery acceptance.

## DSE recommendation

Track each disk’s snapshot sequence and retain its source until the target copy reaches the documented completion state. Give the operator a queue that records creation order, active copy, and next eligible snapshot. Require an explicit check before cleanup so a retention task does not remove a source that is still being copied. Assign responsibility for a stalled sequence rather than silently starting a later snapshot.

## Verification

Record the target snapshot identifier and observed CompletionPercent for each completed transfer. In an approved recovery test, use the completed target to restore a disk and compare its contents with the selected recovery point. Record transfer completion and restoration validation as separate results. Investigate an unexpected order, incomplete target, or content mismatch before accepting the regional copy as usable recovery material.

## Official references

[Microsoft Learn: Copy an incremental snapshot to a new region](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-copy-incremental-snapshot-across-regions). Source reviewed September 9, 2026.

## Primary reference

- Name: Copy a snapshot to a new region - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/disks-copy-incremental-snapshot-across-regions
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Wait for ordered snapshot copies to finish before accepting a regional recovery copy,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/
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.