Exchange DAG Replication Status Failure

Good day,

I checked the status on our exchange server this morning and found that the database failed over yesterday. It was a network relalted issue which has been resolved.

The Cluster network failed and reset itself so I had to reconfigure my cluster network - passing diagnostics now. However when running
Test-replicationhealth I still get database redundancy errors. When checking in the EAC each copy of the database says healthy.

See below pictures - Will this resolve itself?

redundancy.PNG
health-status.PNG

Please Advise?
LVL 5
Leroy LuffHead of IT & DIgitalAsked:
Who is Participating?
 
Marwan OsmanCommented:
please run this cmd to check the status of the databases (don't rely on their status in EAC)

Get-MailboxDatabaseCopyStatus -Server mbxservername | Format-List
0
 
Marwan OsmanCommented:
Run the cmdlet: This will seed the DB to the second server

Add-Mailboxdatabasecopy DBname –MailboxServer servername
Wait for the database copies to become healthy.

http://msexchangeguru.com/2013/02/12/e2013-auto-reseed/
0
 
Leroy LuffHead of IT & DIgitalAuthor Commented:
Hey Mar

But the second server has the database already and as shows it shows healthy as in image above.

Do I need to remove it 1st and then do the seed?

Regards
0
 
Leroy LuffHead of IT & DIgitalAuthor Commented:
By formatting the list I could see the exact error. IT was the public folder database that needed reseeding.

All resolved now.

Thank you
0
 
Marwan OsmanCommented:
Good
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.