lost log files of passive DAG copy

Hello All,

We have two exchange servers 2010 SP3 with DAG setup. Each server contains two mailbox database as primary and two as secondary. We got notified that one server is facing a hardware raid problem. So we activated all four databases on the good one to find out the problem of the faulty server. All database are mounted on one server. After troubleshooting the faulty server, we found out the array relating to log files only is lost but database files and operating system are functioning. We have a backup of lost log partition 4 days ago using exchange backup "networker"

Now the status is all clients are connected to one good server contains all databases while other server has copy status "servicedown". I checked the services of replication and found they are down.

 I read about replay log files from good server to faulty server and another solution about reseed the database from good one. Which is better solution and what we need to be considered before creating another partition for log files on the faulty server in terms of manual backup, etc.?
ATMSAsked:
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.

Simon Butler (Sembee)ConsultantCommented:
I would reseed the database. You will need to do that after you have resolved the hardware issues so that the storage is available for the reseed.
Pretty straight forward process - in most cases Exchange will do all of the work for you.

The backup you have is useless - just reseed. Anything else will confuse Exchange.

Simon.
0
ATMSAuthor Commented:
Dear Simon,

Thank you for your reply. How about the option of index catalog ? and do I need to backup the DAG mailbox db of the faulty server before reseeding.
0
Simon Butler (Sembee)ConsultantCommented:
There is no point doing a backup of the faulty server.
The index catalog should sort itself out once the reseed is complete. Don't worry if it is says it is unhealthy until a good couple of hours (depending on the size of the database) after the reseed is complete.

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
Storage Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.