DAG - Passive Disconnected and resynchronizing

Exchange 2013, I have 24 DBs, 4 of them have this issue

Suspend/Resume does not help

Susoend/Update gives me this error

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'Exch13Server1.domain.com'. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).
 [Database: DB01, Server: Exch13Server2.domain.com]
nourbenAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
The only fix I have found when it reaches that point is to remove the copy completely and do a fresh seed.

Simon.
0
nourbenAuthor Commented:
I have tried that , removed the copy, deleted the files, added a copy and got the same error.
0
Simon Butler (Sembee)ConsultantCommented:
Did you do a backup?
So drop the copy complete, delete the files, then do a backup.
Once the backup is complete, put the copy back.

Circular logging can kind of achieve the same result, but of course that increases the risk of data loss in the event of a database failure at the wrong moment.

The other fix I seem to do more often than not is to simply create a new database, add it to the DAG, then move the users in to the new database, dropping the original afterwards.

Simon.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

nourbenAuthor Commented:
I have 6 new Exchange 2013 servers, I don't have any data yet, these are blank databases
0
Simon Butler (Sembee)ConsultantCommented:
If they are blank databases, then just trash the databases and recreate.

Simon.
0
nourbenAuthor Commented:
I did delete the databases, deleted all files, folders, recreated everything and the same issue.
0
Simon Butler (Sembee)ConsultantCommented:
That would suggest the problem is outside of Exchange.
Do you have anything else on the servers? AV software for example? If so, are the correct exclusions for an Exchange server in place?

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.