<div>
Run the cmdlet: This will seed the DB to the second server<br />
<br />
Add-Mailboxdatabasecopy DBname –MailboxServer servername<br />
Wait for the database copies to become healthy.<br />
<br />
<a href="http://msexchangeguru.com/2013/02/12/e2013-auto-reseed/" rel="ugc">http://msexchangeguru.com/2013/02/12/e2013-auto-reseed/</a>
</div>


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/ [http://msexchangeguru.com/2013/02/12/e2013-auto-reseed/]

<div>
Hey Mar<br />
<br />
But the second server has the database already and as shows it shows healthy as in image above.<br />
<br />
Do I need to remove it 1st and then do the seed?<br />
<br />
Regards
</div>


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

<div>
By formatting the list I could see the exact error. IT was the public folder database that needed reseeding.<br />
<br />
All resolved now.<br />
<br />
Thank you
</div>


By formatting the list I could see the exact error. IT was the public folder database that needed reseeding.

All resolved now.

Thank you

<div>
<div class="content wysiwyg-content">
Good day,<br />
<br />
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.<br />
<br />
The Cluster network failed and reset itself so I had to reconfigure my cluster network - passing diagnostics now. However when running <br />
Test-replicationhealth I still get database redundancy errors. When checking in the EAC each copy of the database says healthy.<br />
<br />
See below pictures - Will this resolve itself?<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2015/05_w20/913491/redundancy.PNG" target="_blank" title="redundancy.PNG (10 KB)"><img alt="redundancy.PNG" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2015/05_w20/800_913491/redundancy.PNG" /></a><br />
<a href="https://filedb.experts-exchange.com/incoming/2015/05_w20/913492/health-status.PNG" target="_blank" title="health-status.PNG (24 KB)"><img alt="health-status.PNG" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2015/05_w20/800_913492/health-status.PNG" /></a><br />
<br />
Please Advise?
</div>
</div>


redundancy.PNG

health-status.PNG

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?






Please Advise?

Exchange DAG Replication Status Failure

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.