{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/", "slug": "dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica", "url": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/" }, "title": "Validate both clusters before pairing them with Storage Replica", "summary": "What should be established independently at each endpoint of cluster-to-cluster replication?", "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:14+00:00", "modified_at": "2026-09-08T18:20:21+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 212, "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.", "primary_source": { "name": "Cluster-to-cluster storage replication", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/cluster-to-cluster-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

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Cluster-to-cluster storage replication. Source reviewed September 8, 2026.

", "content_text": "Source facts\nStorage 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.\nApplicability\nUse 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.\nDSE recommendation\nMaintain 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.\nVerification\nRun 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.\nOfficial references\nMicrosoft Learn: Cluster-to-cluster storage replication. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nStorage 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).\n\n## Applicability\n\nUse 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.\n\n## DSE recommendation\n\nMaintain 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.\n\n## Verification\n\nRun 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.\n\n## Official references\n\n[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." }, "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-057-validate-both-clusters-before-pairing-them-with-storage-replica/", "url": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Validate both clusters before pairing them with Storage Replica", "item": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/", "url": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/", "headline": "Validate both clusters before pairing them with Storage Replica", "description": "What should be established independently at each endpoint of cluster-to-cluster replication?", "abstract": "What should be established independently at each endpoint of cluster-to-cluster replication?", "articleBody": "Source facts\nStorage 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.\nApplicability\nUse 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.\nDSE recommendation\nMaintain 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.\nVerification\nRun 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.\nOfficial references\nMicrosoft Learn: Cluster-to-cluster storage replication. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:14+00:00", "dateModified": "2026-09-08T18:20:21+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-057-validate-both-clusters-before-pairing-them-with-storage-replica/" }, "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-057-validate-both-clusters-before-pairing-them-with-storage-replica/#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": "Validate both clusters before pairing them with Storage Replica" }, "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": 212, "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": "Cluster-to-cluster storage replication", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/cluster-to-cluster-storage-replication" } } ] } }