One of my clients is running into an issue. When you open failover cluster management, and expand networks, the cluster network 1[internal or heartbeat] interfaces are down, and the cluster network 2 somebody accidentally changed the IP and the ip address for the MAPI connection is wrong
There is a major outage, replication is stopped, users have no access to email, we did reboot all mbx servers and with no luck
Here is my question
I would like to remove the cluster networks from cluster management and create new cluster networks with the right NICs and IPs and only if is really required to rebuild the DAG
Should I rebuilt the DAG? IF so what are the steps to remove the cluster network , and rebuild the DAG?
Our exchange environment is Exchange 2010 SP3, OS Windows 2008 R2, all VMs
I found something online to rebuild a DAG, but need the opinion from an expert to validate all steps. Please provide as much details as you can
Removing a node from the DAG.
Steps to follow:
1. Depending on the state, suspend database seeding. When failed, suspend via Suspend-MailboxDatabaseCop
y -Identity <mailbox database><nodename>. When status is failed and suspended this is not needed.
2. Remove Database copies of mailbox databases on the failed node. Use Remove-MailboxDatabaseCopy
-Identity <mailbox database><nodename>. Repeat when needed for the other copies.
3. Remove Server from DAG. Remove-DatabaseAvailabilit
er -Identity <DAGName> -MailboxServer <ServerName> -ConfigurationOnly
4. Evict from cluster.
As the cluster is now only one node, the quorum is moved to node majority automatically. The FWS object is removed from the config.
Rebuilding the DAG by adding the removed node back
From MS http://technet.microsoft.com/en-us/library/gg513521%28v=exchg.141%29.aspx
From a blog:
Steps to follow:
1. Add server to DAG. This will add the node back to the cluster. Add-DatabaseAvailabilityGr
oupServer -Identity <DAGName> -MailboxServer <ServerName>. Succes the node is healthy.
2. Add the database copies as preference 2 (the other node is still active). Add-MailboxDatabaseCopy –Identity <Mailbox Database> -MailboxServer <ServerName> -ActivationPreference 2.
3. In my case to time between fail state and returning to the DAG was a bit long. The database came up, but returned to failed state. We have to suspend and manually seed. Suspend-MailboxDatabaseCop
y -Identity <mailbox database><nodename>.
-Identity “<Mailbox Database><Mailbox Server>” -DeleteExistingFiles. Wait for the bytes are transferred across the line. When finished the suspended state is automaticaly lifted.
Repeat for the other databases.
5. You will now see a good state of the DAG and databases in Exchange Management console. Not yet. The file witness share is not yet back.
6. Add the Witness share from Exchange powershell. Set-DatabaseAvailabilityGr
oup -WitnessDirectory “<Server Directory” -WitnessServer “<Servername>” -id “<DAG Name>”. When the DAG members are minimal two the FWS is recreated. This is also visible in Failover Cluster.