Database status Bad copy count "1" -Exchange 2013

I am using exchange 2013. There are two mailbox servers which are in DAG. Database is mounted and healthy. All seems good. To configure a DR Site, I created an exchange 2013 on azure cloud and synced one database. When I started second database sync, it got failed saying below error. When I check database status, It shows me "Bad copy count" status is 1. While database is mounted and healthy.


The seeding operation failed. Error: An error occurred while performing the seed operation. Error: An error occurred while communicating with server 'TTAEXCH2013C1'. Error: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [Database: MailboxDB_Users3, Server: Exchange2013-DR.TTA.MUMBAI.COM]
Arif KhanSystem AdministratorAsked:
Who is Participating?

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

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.

it seems you have unhealthy databasecopystatus,. Kindly check the copy status of all DBs
Arif KhanSystem AdministratorAuthor Commented:
There are only three DBs. Two are OK. I am getting this error on only single DB.
Try to restart the MS replication service on affected server and run the copy again

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
Arif KhanSystem AdministratorAuthor Commented:
I restarted the MS replication service and resumed but getting failed. Again I have started full sync, is it fine.
I think something is wrong with database . How can I fix that bad count 1?
Muhammad AsifSenior Solutions ArchitectCommented:
Hi Arif,

BAD count means that your third copy of effected mailbox database is not healthy or not in properly created in Azure Exchange server. You may delete the passive copy of database on Azure Exchange server and then retry to add it.
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

From novice to tech pro — start learning today.