# Distinguish an intentionally dismounted Storage Replica destination from a failed copy

> How should replication progress be checked when a destination volume is not mounted?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:29+00:00
- Modified: 2026-09-08T18:17:14+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

How should replication progress be checked when a destination volume is not mounted?

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

## Article

## Source facts

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](https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/server-to-server-storage-replication).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

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

## Primary reference

- Name: Server-to-Server Storage Replication
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/server-to-server-storage-replication
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Distinguish an intentionally dismounted Storage Replica destination from a failed copy,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-042-distinguish-an-intentionally-dismounted-storage-replica-destination-from-a-failed/
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.