locked
Server 2016 Multi-site stretch cluster with storage Replica RRS feed

  • Question

  • Hi

    We are busy implementing a 4 node SQL Cluster using storage replica, 2 nodes per GEO site  Lonndon-DC(LDC) -Amesterdam-DC (ADC) and -using Async 

    All the configuration was done and storage replica was enabled -> Source(LDC)  - Log Source(LDC) - Log Destination(ADC) - Destination(ADC) wizard went through

    I can also see all Source and destination volumes are the same size

    Normal movement of cluster roles work fine

    The problem we are experiencing is that when we try and simulate a site DR and bring down the two nodes in (LDC) the storage replication does not fail over and do the reverse replication - with this SQL role will fail - when we bring up the (LDC) back up the roles go back online and replication carries on

    Is there additional configuration to be done or do you have to run a script to reverse replication direction  

     

    Monday, April 24, 2017 9:29 AM

All replies

  • Hi Sir,

    Have you configured quorum for that cluster ?

    https://docs.microsoft.com/en-us/windows-server/storage/storage-replica/stretch-cluster-replication-using-shared-storage

    Best Regards,

    Elton


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Elton_Ji Wednesday, May 10, 2017 10:53 PM
    Saturday, May 6, 2017 3:28 AM
  • Hi 

    The quorum for the cluster was configures to a file share on Azure VM

    All the hosts are able to see the quorum

    We can fail the the cluster over to any host with no problem

    all hosts do have a vote as well

    we can also see the storage on the replication side is there

    "The asynchronous destination now meets the configured Recovery Point Objective (RPO)."

    Kind regards 

    Louis

    Tuesday, May 16, 2017 5:23 AM
  • Hi Louis, 

    Have you gotten any resolution on this problem? we are facing the exact same issues with Stretch Cluster Asynchronous replication. 

    After digging a bit, we found out that this is a known issue with Windows Server 2016 Build 1607. But I am hoping you found a work around for this problem and could help us maybe?

    • Proposed as answer by Maru1130 Tuesday, November 13, 2018 8:12 AM
    • Unproposed as answer by Maru1130 Tuesday, November 13, 2018 8:12 AM
    Wednesday, February 28, 2018 3:38 PM
  • Hi All,

    When you are using Cluster for Storage replica Asynchronous is not recommended. If you are using Asynch, you need to do Set-SRPartnership to move to the DR site. Unlike when your replication is Synchronous, automatic failover is allowed. 

    Thanks,

    Tuesday, November 13, 2018 8:15 AM