Share via

Can't recover a DAG member

Mikhail Firsov 1,876 Reputation points
2023-04-28T14:10:10.2066667+00:00

Hello!

The theory:

"If the DAG member being removed is offline and can't be brought online, you must add the -ConfigurationOnly parameter to the preceding command. If you use the -ConfigurationOnly switch, you must also manually evict the node from the cluster."

I have successfully evicted the failed node from the cluster but Setum /m:RecoverServer keeps complaining "...~This server is DAG member...":
Q2

What else can I do to start recovering the server?

Thank you in advance,
Michael

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,510 questions
Microsoft Exchange
Microsoft Exchange
Microsoft messaging and collaboration software.
467 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Kael Yao-MSFT 37,681 Reputation points Microsoft Vendor
    2023-05-01T06:58:09.66+00:00

    Hi @Mikhail Firsov

    I have successfully evicted the failed node from the cluster but Setum /m:RecoverServer keeps complaining "...~This server is DAG member...":

    Would you please share the detailed steps of removing the node from cluster?

    If you check the current membership of the DAG in EAC or via EMS, would you still see the failed node as a member?

    If yes, please remove the node from DAG via the Remove-DatabaseAvailabilityGroupServer cmdlet in EMS on another member server and retry recover.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Mikhail Firsov 1,876 Reputation points
    2023-05-02T09:07:46.0066667+00:00

    Hi Kael Yao-MSFT,

    Sorry - forgot to mention: that command - "Remove-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer MBX1 -ConfigurationOnly" had failed also so I had to evict the node from WFC manually (Evict the node...). I thought this action (the node's removal) would update the EXCH1's property in AD in such the way that AD "would know" the EXCH1 is no longer the cluster node, but seems I was wrong...