Storage Replica Cluster to Cluster support with Automatic VM Orchastrated Fail-over
To provide the Ultimate Disaster Recovery solution across separate clusters for Active/Active scenarios (same HW) or Active Passive scenarios (different HW), Providing a One to Many placement via Synchronous/Asynchronous Replication, providing RPO/RTO of choice, and to automatically Orchestrate failover of VM's to destination of choice with the RTO of choice, to patch and complete lifecycle management on each cluster without impact to overall service.
Why is Cluster to Cluster DR solution important, A Stretch Cluster can still suffer issues at the Hyper-V level and impact the whole cluster, the same for life cycle management and patching, requires the same hardware configuration and be symmetrical and unlikely to support one to many replication configurations.
Yes! We want this. In Sweden almost the entire public sector and a large part of the private sector have 7x24 requirements on core IT systems. Other solutions - competing and traditional Hyper-V clusters - offer cluster solutions with zero data loss and automated failover whereas management and orchestration of storage replica for S2D/Azure Stack HCI is too complex resulting in backup/restore solutions instead. But that only covers requirements on the level of 5+ years ago!
Lane Crawley commented
Customers willing to spend the money on S2D feel its reasonable to expect replication should be included or an easy next step.
For the sake of regulations, many of them must have a copy of their data off-site and would prefer that doesn't involve learning the another product to do so.
Ketil Neteland commented
This functionality is essential for Enterprise customers. The customers avoid the solution just because of this missing functionality.
Andreas Falck commented
When building DR solutions for customer, this missing functions sometimes stops the hole project when we want to use S2D Cluster to Cluster replications.
Ben Thomas (NZ) commented
Agreed. This sort of capability should be part of cluster sets, which is aware of multiple clusters already and what is running on them. It's a logical extension