Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Tech Book—Dell Integrated System For Microsoft Azure Stack HCI
Preface Business Transformation and Data Center Modernization Evolution of Data Centers to HCI and Hybrid Cloud A Closer Look at Microsoft Azure Stack HCI Azure Stack HCI Architecture and Building Blocks Dell Integrated System for Microsoft Azure Stack HCI Portfolio – AX Nodes Networking Topologies for Azure Stack HCI Solutions Stretch Clustering with Azure Stack HCI
Stretch Clustering with Azure Stack HCI
Azure Stack HCI stretch clustering
Comparison of traditional and stretched clusters
Business continuity planning
Stretch clustering topology
Servers Storage pools Volumes Setup configuration Preferred site configuration Affinity and anti-affinity VMs Cloud witness
Azure Stack HCI stretch clustering scenarios and concepts
Active/passive setup Active/Active Synchronous replication Asynchronous replication
Stretch clustering best practices with Azure Stack HCI
Validated network topology
Basic configuration High throughput configuration Server and site affinity rules for VMs
Managing the Hybrid Cloud Sizing and Configuration Best Practices Dell Support and Services Conclusion Additional Resources

Azure Stack HCI stretch clustering scenarios and concepts

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > Guides 22H2 and earlier > Tech Book—Dell Integrated System For Microsoft Azure Stack HCI > Azure Stack HCI stretch clustering scenarios and concepts

Azure Stack HCI stretch clustering scenarios and concepts

  • Asynchronous replication

    Mirrors data across greater distances over networks with higher latencies. This strategy does not guarantee that both sites have identical copies of the data at the time of failure. This replication technique does not enable workloads to be brought back online automatically after a failover. With asynchronous replication, the remote node accepts blocks of replicated data and lazily acknowledges back to the source copy.