# Validate both clusters before pairing them with Storage Replica

> What should be established independently at each endpoint of cluster-to-cluster replication?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:14+00:00
- Modified: 2026-09-08T18:20:21+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

What should be established independently at each endpoint of cluster-to-cluster replication?

## Potentially affected

Use this review for a proposed cluster-to-cluster volume-replication design.

## DSE recommendation

Maintain separate readiness records for the two clusters and a third record for the intercluster path.

## Article

## Source facts

Storage Replica supports volume replication between clusters, including clusters using Storage Spaces Direct. Microsoft says Test-SRTopology can evaluate many requirements after the relevant feature or management tools are installed; a replication relationship is not required to use the tool. Its procedure configures, validates, and tests both failover clusters before replicating them. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/cluster-to-cluster-storage-replication).

## Applicability

Use this review for a proposed cluster-to-cluster volume-replication design. Identify both cluster identities, selected volumes, management hosts, and network path. Match the planned configuration to the full current prerequisites before pairing endpoints.

## DSE recommendation

Maintain separate readiness records for the two clusters and a third record for the intercluster path. Name the owners responsible for resolving validation findings at each site. Review the proposed source and destination direction with the storage owner, including the handling of destination data. Keep the topology assessment and workload recovery objectives together in the deployment decision.

## Verification

Run the approved readiness and topology checks, then retain their actual results for both endpoints. After authorized configuration, verify the relationship and a controlled data-change test. Record the cluster roles and volumes involved so the result cannot be mistaken for a different pairing. Resolve any endpoint or path finding before scheduling a recovery exercise.

## Official references

[Microsoft Learn: Cluster-to-cluster storage replication](https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/cluster-to-cluster-storage-replication). Source reviewed September 8, 2026.

## Primary reference

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

## Citation and use

Preferred citation: “Validate both clusters before pairing them with Storage Replica,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/
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.