{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/", "slug": "dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed", "url": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/" }, "title": "Distinguish an intentionally dismounted Storage Replica destination from a failed copy", "summary": "How should replication progress be checked when a destination volume is not mounted?", "format": { "slug": "guide", "name": "Guide" }, "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-08T18:16:29+00:00", "modified_at": "2026-09-08T18:17:14+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 203, "potentially_affected": "Use this review when assessing an existing server-to-server relationship.", "dse_recommendation": "Record the relationship and replica-group state before attempting any corrective change.", "primary_source": { "name": "Server-to-Server Storage Replication", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/server-to-server-storage-replication", "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 documents server-to-server Storage Replica as synchronization of a volume between two servers. Destination volumes and their drive letters or mount points are deliberately dismounted by Storage Replica. The destination replica group exposes the remaining byte count for progress inspection. Microsoft documents Get-SRPartnership and Get-SRGroup for checking the actual replication endpoints and state. Microsoft documentation.

\n

Applicability

\n

Use this review when assessing an existing server-to-server relationship. Identify its current source, destination, and volumes before interpreting a missing destination drive letter as a storage failure.

\n

DSE recommendation

\n

Record the relationship and replica-group state before attempting any corrective change. Examine copy progress and the relevant replication events together. Keep a source/destination worksheet with the investigation so the intended passive endpoint is unmistakable. Do not authorize a direction change solely to make the destination visible for an informal file inspection.

\n

Verification

\n

Compare repeated progress observations and recorded events with the agreed monitoring criteria. Investigate errors or lack of expected progress through the matching source procedure. If recovery testing is required, arrange it as a separate approved exercise. Preserve the endpoint identities, observations, and conclusion so intentional dismounting remains distinguishable from a later genuine failure.

\n

Official references

\n

Microsoft Learn: Server-to-Server Storage Replication. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft documents server-to-server Storage Replica as synchronization of a volume between two servers. Destination volumes and their drive letters or mount points are deliberately dismounted by Storage Replica. The destination replica group exposes the remaining byte count for progress inspection. Microsoft documents Get-SRPartnership and Get-SRGroup for checking the actual replication endpoints and state. Microsoft documentation.\nApplicability\nUse this review when assessing an existing server-to-server relationship. Identify its current source, destination, and volumes before interpreting a missing destination drive letter as a storage failure.\nDSE recommendation\nRecord the relationship and replica-group state before attempting any corrective change. Examine copy progress and the relevant replication events together. Keep a source/destination worksheet with the investigation so the intended passive endpoint is unmistakable. Do not authorize a direction change solely to make the destination visible for an informal file inspection.\nVerification\nCompare repeated progress observations and recorded events with the agreed monitoring criteria. Investigate errors or lack of expected progress through the matching source procedure. If recovery testing is required, arrange it as a separate approved exercise. Preserve the endpoint identities, observations, and conclusion so intentional dismounting remains distinguishable from a later genuine failure.\nOfficial references\nMicrosoft Learn: Server-to-Server Storage Replication. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft documents server-to-server Storage Replica as synchronization of a volume between two servers. Destination volumes and their drive letters or mount points are deliberately dismounted by Storage Replica. The destination replica group exposes the remaining byte count for progress inspection. Microsoft documents Get-SRPartnership and Get-SRGroup for checking the actual replication endpoints and state. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/server-to-server-storage-replication).\n\n## Applicability\n\nUse this review when assessing an existing server-to-server relationship. Identify its current source, destination, and volumes before interpreting a missing destination drive letter as a storage failure.\n\n## DSE recommendation\n\nRecord the relationship and replica-group state before attempting any corrective change. Examine copy progress and the relevant replication events together. Keep a source/destination worksheet with the investigation so the intended passive endpoint is unmistakable. Do not authorize a direction change solely to make the destination visible for an informal file inspection.\n\n## Verification\n\nCompare repeated progress observations and recorded events with the agreed monitoring criteria. Investigate errors or lack of expected progress through the matching source procedure. If recovery testing is required, arrange it as a separate approved exercise. Preserve the endpoint identities, observations, and conclusion so intentional dismounting remains distinguishable from a later genuine failure.\n\n## Official references\n\n[Microsoft Learn: Server-to-Server Storage Replication](https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/server-to-server-storage-replication). Source reviewed September 8, 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-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/", "url": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Distinguish an intentionally dismounted Storage Replica destination from a failed copy", "item": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/", "url": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/", "headline": "Distinguish an intentionally dismounted Storage Replica destination from a failed copy", "description": "How should replication progress be checked when a destination volume is not mounted?", "abstract": "How should replication progress be checked when a destination volume is not mounted?", "articleBody": "Source facts\nMicrosoft documents server-to-server Storage Replica as synchronization of a volume between two servers. Destination volumes and their drive letters or mount points are deliberately dismounted by Storage Replica. The destination replica group exposes the remaining byte count for progress inspection. Microsoft documents Get-SRPartnership and Get-SRGroup for checking the actual replication endpoints and state. Microsoft documentation.\nApplicability\nUse this review when assessing an existing server-to-server relationship. Identify its current source, destination, and volumes before interpreting a missing destination drive letter as a storage failure.\nDSE recommendation\nRecord the relationship and replica-group state before attempting any corrective change. Examine copy progress and the relevant replication events together. Keep a source/destination worksheet with the investigation so the intended passive endpoint is unmistakable. Do not authorize a direction change solely to make the destination visible for an informal file inspection.\nVerification\nCompare repeated progress observations and recorded events with the agreed monitoring criteria. Investigate errors or lack of expected progress through the matching source procedure. If recovery testing is required, arrange it as a separate approved exercise. Preserve the endpoint identities, observations, and conclusion so intentional dismounting remains distinguishable from a later genuine failure.\nOfficial references\nMicrosoft Learn: Server-to-Server Storage Replication. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:29+00:00", "dateModified": "2026-09-08T18:17:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/" }, "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-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/#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": "Distinguish an intentionally dismounted Storage Replica destination from a failed copy" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "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": 203, "timeRequired": "PT1M", "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": "Server-to-Server Storage Replication", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/server-to-server-storage-replication" } } ] } }