Ghost-member in DAG

Hello!

I had 3 servers (all Win2012 and Exchange 2013 CU8):
mail.example.com (CAS server, witness server)
mbx1.example.com (mailbox server, DAG member)
mbx2.example.com (mailbox server, DAG member).

I wanted to update to CU9, used StartDAGServerMaintenance.ps1 in MBX1
I lost the machine. Decided to behave by https://technet.microsoft.com/en-us/library/dd638206%28v=exchg.150%29.aspx

setup.exe /m:RecoverServer was fine but I couldn't add the mbx1 to DAG (named mbxdag) member.
I made "Remove-MailboxDatabaseCopy MbDb1\Mbx1" and "Remove-DatabaseAvailabilityGroupServer -Identity mbxdag -MailboxServer Mbx1 -ConfigurationOnly"

OK, uninstalled this machine. Installed mbx3. Before adding this to DAG member I want to make the system clean.

If I click Edit in ECP->DAG, then it says "The fully qualified domain name for node 'mbx1' could not be found."
There is some information about mbx1 somewhere.
Get-DatabaseAvailabilityGroup still shows only
Name             Member Servers                                      Operational Servers
----             --------------                                      -------------------
mbxdag           {MBX2}

I made little surfing in ADSIedit. I found nothing about MBX1. Of course it does not mean that there is not anything. Should I restart any service (in MBX2 or in MAIL)?

  • Edited by lote_msdnaa Friday, July 24, 2015 8:17 PM More details
July 24th, 2015 4:02pm

I hate to recommend it, but I would certainly restart MBX2 before doing anything else.  It's very possible that something is cached.  Also look in Failover Cluster Manager to see if there is any trace of MBX1 there.
Free Windows Admin Tool Kit Click here and download it now
July 25th, 2015 8:58pm

I have discovered something new for me:) In Failover Cluster manager I could connect to DAG and there was the possibility to evict the node MBX1. Amazing!
  • Marked as answer by lote_msdnaa 1 hour 20 minutes ago
July 27th, 2015 2:10am

Hi,

According to your description, do you remove the MBX1 from cluster node?
If not, please run Get-ClusterNode MBX1 | Remove-ClusterNode -Force to remove.
Note: you need to import the Failover Cluster module into your Exchange Management Shell session to perform this task.

How about run command to add MBX3 to DAG? It retrun something wrong, please post here for further troubleshooting.

Thanks

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 3:16am

I have discovered something new for me:) In Failover Cluster manager I could connect to DAG and there was the possibility to evict the node MBX1. Amazing!
  • Marked as answer by lote_msdnaa Monday, July 27, 2015 6:08 AM
July 27th, 2015 6:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics