none
2 node cluster site resilience failure RRS feed

  • Question

  • Env: Exchange 2016

    Production site MBX with witness, RD site MBX with alternative witness

    During Production site failure execute below site failover procedure get fail. May i know 2 node dag with 2 site is it not support or our procedure incorrect.

    1. Stop-DatabaseAvailabilityGroup –Identity DAG1 – ActiveDirectorySite PRDSite -ConfigurationOnly
    2. Stop DR cluster service
    3. Restore-DatabaseAvailabilityGroup –Identity DAG1 –ActiveDirectorySite DRSite

    Error Message return when execute step 3

    An error occurred while attempting a cluster operation. Error: Cluster API failed: OpenByNames('DRMBX.demo.local')
    failed for each server. Specific exceptions: 'An error occurred while attempting a cluster operation. Error: Cluster API
    failed: "OpenCluster(DRMBX.demo.local) failed with 0x6d9. Error: There are no more endpoints available from the
    endpoint mapper"'.
        + CategoryInfo          : NotSpecified: (:) [Restore-DatabaseAvailabilityGroup], ClusterApiException
        + FullyQualifiedErrorId : [Server=DRMBX,RequestId=4a122a56-fff4-4ac3-81f5-b4cdf6a2de44,TimeStamp=2/12/2020 5:24:46
        AM] [FailureCategory=Cmdlet-ClusterApiException] 7BEA8645,Microsoft.Exchange.Management.SystemConfigurationTasks.Restore
      DatabaseAvailabilityGroup
        + PSComputerName        : DRMBX.demo.local

    Thursday, February 13, 2020 2:12 AM

All replies

  • In case of activationg DR site you need to perform Datacenter switchovers

    Please read and understand and execute stepby step

    https://docs.microsoft.com/en-us/exchange/high-availability/manage-ha/datacenter-switchovers?view=exchserver-2019


    Vinny | Freelancer | Microsoft Certified Azure Solutions Architect Expert| Microsoft 365 Certified: Enterprise Administrator | Microsoft 365 Certified: Messaging Administrator Associate| ITILV3 | PMP

    Thursday, February 13, 2020 3:04 AM
  • The DAG enabled DAC and already follow datacenter switchovers procedure to stop and restore the service. Get same result. 
    Thursday, February 13, 2020 8:04 AM
  • Hi,

    Which site the witness server is located?

    Do you also configure an alternate witness server? Please make sure the alternative witness server works well and is available.  If the alternate witness server wasn't previously configured, you can configure it by using the AlternateWitnessServer and AlternateWitnessDirectory parameters of the Restore-DatabaseAvailabilityGroup cmdlet:

    Restore-DatabaseAvailabilityGroup -Identity <DAG name> -ActiveDirectorySite <site name> -AlternateWitnessServer <FileShareWitnessServerName> -AlternateWitnessDirectory <NonRootLocalLongFullPath>

    Regards,

    Lydia Zhou


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

    Friday, February 14, 2020 5:13 AM
    Moderator
  • witness server is located on production, alternative witness also well configured on DR site. mentioned command also try before it's get same result.
    Saturday, February 15, 2020 2:27 AM