Exchange 2013

I am getting error "the specified database isn't configured for replication" when adding second Exchange server as database copy. I have dismounted and removed the default database created on Second server and now trying to replicate database after completing DAG and witness configuration
LVL 4
pchettriIT DirectorAsked:
Who is Participating?
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.

Will SzymkowskiSenior Solution ArchitectCommented:
Have you made sure that your Drive letters and paths are identical for both DAG members where you are enabling copies?

Will.
pchettriIT DirectorAuthor Commented:
Yes... I do have f drive in the second server. I thought it was suppose to pick the same drive automatically
Will SzymkowskiSenior Solution ArchitectCommented:
After you add an Exchange server to a DAG you need to enable copies on the DAG member. This does not happen automatically.

Will.

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
pchettriIT DirectorAuthor Commented:
I did not enable database copy that is when I got this error. I can see it did automatically created folder on F drive on second server. I probably have to log ticket to MS to find why it failed. To me the error sounds specific to health of DB or the empty DB I dismounted on second sever and removed or hidden component of existing DB like health monitoring DB based on event logs on both DB
pchettriIT DirectorAuthor Commented:
I just have to run update to resync but  I got same error on test db too until I did update again. Most be an issue related to cluster network object or cluster network. I am kind of suspicious about seeding if it does not pickup automatically and I have run update every time manually. Kind of wasted ms ticket just to press update or may be I will have to setup second network card on both server and ask them to fix on same ticket
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.