jobby1
asked on
exchange 2013 DAG not failing over
I have created the exchange 2013 DAG. But the server is not failing over to the other dag database once the primary server is down. How can we troubleshoot.
Once you created the DAG, did you set up the Database Copy on the secondary server? Not just a second database.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can you provide a screen shot of your databases so we can make sure you have both servers associated with the database? It sounds like you have not added the mailbox database to the DAG. you should see both server names next to the database name. Also make sure you have an IP address assigned to the DAG if you don't use DHCP for this.
ASKER
There is copy in the other server and I can see the logs getting replicated. But the database is not replicating. Is this an issue.
Yes that would be an issue. Are you able to right click the database and hit resume replication?
Do check whether the replication service is running on both the servers.
Also check the queue length of the logs .
what is that status of the passive copy of the database : is it suspended or healthy ?
Also check the queue length of the logs .
what is that status of the passive copy of the database : is it suspended or healthy ?
What's the status of the database on each server? One should say "Active" and the other replicated database should say "Healthy".
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What was the fix?
ASKER
It is ok now
You can check the Replication services by running this command
services.msc
and then check for Microsoft Exchange replication service is in running state or stopped ,
Also you can check the queue length in the GUI in Database availability group
nex to the mailbox store database status as mounted . you will find the queue length
services.msc
and then check for Microsoft Exchange replication service is in running state or stopped ,
Also you can check the queue length in the GUI in Database availability group
nex to the mailbox store database status as mounted . you will find the queue length