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
E2E Deployment and Operations Guide with Stretched Cluster: Integrated System for Microsoft Azure Stack HCI
About using this guide Introduction Solution overview Solution deployment Creating a stretched cluster
Creating a stretched cluster
Introduction
Test-Cluster
Cluster creation
Configuring host networking
Creating a cluster
Configuring a cluster witness
Creating required intents for a stretched cluster
Volumes
Storage efficiency
Test-SRTopology
Virtual Machines Failure/Recovery from failure of Site/Node Appendices Day 1 operations Managing and monitoring clusters with Windows Admin Center Dell OpenManage Integration with Windows Admin Center Updates and maintenance References

Volumes

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > Guides 22H2 and earlier > E2E Deployment and Operations Guide with Stretched Cluster: Integrated System for Microsoft Azure Stack HCI > Volumes

Volumes

  • Replication-enabled volumes can be created using a combination of PowerShell and Failover Cluster Manager or by using Windows Admin Center.

    Note: Install Storage Replica Module for Windows PowerShell (RSAT-Storage-Replica) on the management node with Desktop Experience that is used for installing Windows Admin Center and Failover Cluster Manager to access the cluster.

    Note: Site-to-site volume encryption uses additional CPU resources to encrypt data, and could potentially cause cluster performance-related issues. Microsoft and Dell recommend disabling site-to-site volume encryption unless required.

    For each replica-enabled volume, you need a corresponding log volume on both sites (with a minimum of 8 GB in size) and an equivalent replica volume on the secondary site. The log volume is used to serialize writes for replication.

    The following table shows the volumes that are must create a 1 TB replica volume:

    Table 6. Volumes in a 1 TB replica volume
    Site A Size Site B Size
    VolumeA 1 TB VolumeA-Replica 1 TB
    VolumeA-Log 40 GB VolumeA-Replica-Log 40 GB
    VolumeB 500 GB VolumeB-Replica 500 GB
    VolumeB-Log 40 GB VolumeB-Replica-Log 40 GB

    Once a replicated volume is created, go to Storage Replica > Partnership > Settings > Modify Partnership settings to verify the status of the replica traffic encryption.



    See Appendix A for the correct PowerShell Cmdlets and Failover Cluster Manager steps to create the volumes shown in this table. It is recommended that you create two-way mirrors for all volumes to improve write performance and capacity efficiency.

    Note: For Asynchronous Replication, the RPO can be set as low as 30 s.

    For a planned site failure, when the volume replication direction is reversed, the disk reservations on the secondary site for Replica Volume and Replica-log volumes are removed and moved to the primary site. Source Data and Source Log volumes are given the disk reservations and become active on the secondary site. After 10 minutes, the virtual machines residing on the primary site associated with the migrated volume automatically Live Migrate to the secondary site.