Avatar of jobby1
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.
ExchangeWindows Server 2008Email Clients

Avatar of undefined
Last Comment
I Qasmi

8/22/2022 - Mon
Gareth Gudger

Once you created the DAG, did you set up the Database Copy on the secondary server? Not just a second database.
SOLUTION
I Qasmi

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Sean

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.
jobby1

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.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Sean

Yes that would be an issue. Are you able to right click the database and hit resume replication?
I Qasmi

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 ?
Gareth Gudger

What's the status of the database on each server? One should say "Active" and the other replicated database should say "Healthy".
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
ASKER CERTIFIED SOLUTION
jobby1

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Gareth Gudger

What was the fix?
jobby1

ASKER
It is ok now
I Qasmi

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
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes