Exchange 2010: DAG. Move passive database copy


We have a physical Exchange server that's part of a DAG and it's running critically short of drive space. It is currently hosting the passive copy of a mailbox database.

We've attached an iSCSI LUN to it with sufficient space and my plan is to suspend the database copy, manually move the database files to this new drive on the LUN, rename physical drive to a different drive letter and give the original drive letter to new drive. In theory when we resume the database copy it'll see the database in the 'same' location as before and reseed.

I've done something similar with single instance databases and PF databases where I've dismounted and copied them but am wary that I won't be 'dismounting' the passive database copy so it might not work.

We are trying to minimise downtime so please let me know if my plan above will work?
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.

Simon Butler (Sembee)ConsultantCommented:
If you want to minimise downtime, just remove the copy, shuffle the drives about and then let it reseed.
Unless of course there is some reason why you don't want to do that?

What you want to do should in theory work. I would stop all Exchange services, not just dismount things on the passive server so Exchange is completely dead in the water while you are doing the work.

You are almost doing an offline manual seed, so it should let you do it. Just don't hang about, as the longer you leave it then the higher the chance of a complete reseed being required.


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
niltdAuthor Commented:
Thanks Simon. Will the fact that we have circular logging enabled have any effect on removing the copy, reshuffling the drive and reseeding?
niltdAuthor Commented:
Also, by copying over the database to the new drive after removing the copy, will it recognise it after I re-add the copy and thus only seed the changes and not the whole thing? The DB is 350GB so would take a while to seed...
Simon Butler (Sembee)ConsultantCommented:
If you remove the copy and add it back in then it will do a complete reseed.
Circular logging doesn't make a difference - but you do need to have enough space as the logs will build up while the data is being moved around.

niltdAuthor Commented:
Thanks Simon. I took your advice and removed the database copy, moved the drive letters around and then re-seeded. It worked a charm and there was zero downtime and disruption to users.
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.