{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/", "slug": "dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery", "url": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/" }, "title": "Wait for ordered snapshot copies to finish before accepting a regional recovery copy", "summary": "When is a managed cross-region incremental snapshot copy ready for restoration?", "format": { "slug": "checklist", "name": "Checklist" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-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": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "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:31:07+00:00", "modified_at": "2026-09-10T00:32:01+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 254, "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.", "primary_source": { "name": "Copy a snapshot to a new region - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-copy-incremental-snapshot-across-regions", "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

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Copy an incremental snapshot to a new region. Source reviewed September 9, 2026.

", "content_text": "Source facts\nMicrosoft’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.\nApplicability\nApply 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.\nDSE recommendation\nTrack 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.\nVerification\nRecord 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.\nOfficial references\nMicrosoft Learn: Copy an incremental snapshot to a new region. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nMicrosoft’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).\n\n## Applicability\n\nApply 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.\n\n## DSE recommendation\n\nTrack 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.\n\n## Verification\n\nRecord 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.\n\n## Official references\n\n[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." }, "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-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/", "url": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Wait for ordered snapshot copies to finish before accepting a regional recovery copy", "item": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/", "url": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/", "headline": "Wait for ordered snapshot copies to finish before accepting a regional recovery copy", "description": "When is a managed cross-region incremental snapshot copy ready for restoration?", "abstract": "When is a managed cross-region incremental snapshot copy ready for restoration?", "articleBody": "Source facts\nMicrosoft’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.\nApplicability\nApply 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.\nDSE recommendation\nTrack 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.\nVerification\nRecord 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.\nOfficial references\nMicrosoft Learn: Copy an incremental snapshot to a new region. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:31:07+00:00", "dateModified": "2026-09-10T00:32:01+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/" }, "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-049-wait-for-ordered-snapshot-copies-to-finish-before-accepting-a-regional-recovery/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Wait for ordered snapshot copies to finish before accepting a regional recovery copy" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Checklist", "Information priority" ], "genre": "Checklist", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 254, "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": "Copy a snapshot to a new region - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-copy-incremental-snapshot-across-regions" } } ] } }