Hello Exchange experts/guru/saviors of my stress!!!!!!
I have been racking my brain on how to fix this issue where one database "SA-DB01" will not replicate to the DR server. The copy queue length keeps growing.
Event ID errors are:
Event ID 4138 MSExchange Repl
Event ID 4374 MSExchange Repl
Event ID 4113 MSExchange Repl
Event ID 1009 MSExchangeFastSearch
Here is my Attempts step by step:
SA-DB01 will not replicate to the DR server. The copy queue keeps growing and the database is on passive failed and suspended.
Attempt Fix 1: Ran an Update-MailboxDatabaseCopy "SA-DB01\SA-EXDR-P01" -DeleteExistingFiles -BeginSeed -SourceServer SA-EX-P01
The copy queue length seems to increase as the seeding is taking place. Then it runs fine for 2-4 hours then craps out me with the error below.
“The seeding operation failed. Error: An error occurred while performing the seed operation. Error: An error occurred while communicating with server 'SA-EX-P01'. Error: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.”
The Database then goes to back to passive failed and suspended. I try to do resume and get the following error:
“The Microsoft Exchange Replication service encountered an error while inspecting the logs and database for SA-DB01\SA-EXDR-P01 on startup. Error: File check failed : Database file 'F:\SA-DB01\SA-DB01.edb' was not found.”
Sure enough, the edb wasn’t there.
Attempt fix 2: I remove the old DR database copy and start a new one. I select that it copies from SA-EX-P01. Sure enough, after 4 hours, it will fail and go back to passive failed and suspended. I hit resume and the get the same error above.
I ran a health database test against SA-DB01 on SA-EX-P01 (production) and everything checked out find.
Attempt fix 3: Restarted the MS exchange fast search and MS exchange replication server. Tried to reseed again but got the same error above.
Attempt fix 4: I reboot my DR and P01 server, thinking this will work and tried to run another reseed. Sure enough, after 4 hours, the copy craps out on my and I get the same error above.
Workaround/Testing: I created a new database and did a copy to the DR, all worked fine. I moved my mailbox there and it copied to the new database with no problems and it can replicate to the DR server.
Workaround for queue length: Enabled Windows backup and it decreased the queue length from 40k to 10k.
Seems to be just one database can’t replicate to the DR server. All the other ones will replicate with no issues. I would hate to think that it is a database problem. If it is, I would have to move all mailboxes from SA-DB01 to SA-DB05. At this point, I don’t know what else to try. Can anyone help or have experience with this problem?