Link to home
Create AccountLog in
Avatar of bjennings
bjennings

asked on

How to move large exchange 2003 database

Hello Everyone,

I am going to be moving our exchange server  2003 mailstore and public folders to a new storage array.  The amount of data is over 200 gig, so I want some advice on the easiest way to move these files to the storage array.  Can I  dismount the store and then copy the mailstore and public folders to the storage array?  Does anyone know how long would that take?

Thanks,

Bill
Avatar of waleeda
waleeda
Flag of Qatar image

please read the below article from Microsoft

How to move Database and Logs Files in Exchange 2003

http://support.microsoft.com/kb/821915

ASKER CERTIFIED SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
I agree with leew, create a new store and move the mailboxes.

no downtime
nice clean defragmented database free of errors
Avatar of bjennings
bjennings

ASKER

Hello Leew...I want to make sure I understand.  After I have installed the storage array and created the LUN; I will then go to my exchange server and create a new mail store on the LUN.  Then I would just move the mailboxes and public folder over to the new store.
@ demazter
How u r telling there is no downtime
During moving the mailboxes the use could not access the mailbox
Also for the offline defragmentation the databse will be down,
Take care bjennings
Yes you are right, there is downtime for the single mailbox that is being moved at that particular time, this is not for ALL users at the same time that it would be if you moved the entire mailstore.

waleeda, If you actually read my post, you will see there is no mention of offline defragmentation, and if you have read my offline defrag article or seen any of my other posts you will know that I NEVER recommend an offline defragmentation of a mailstore.

>>> I will then go to my exchange server and create a new mail store on the LUN.  Then I would just move the mailboxes and public folder over to the new store.

That is correct, with one exception, you can only have one public folder store so you will have to move that, which will create downtime.
There is no significant downtime.  Downtime is per user and because a user's mailbox can usually be moved in a few minutes, it's quite possible the user would never know (especially if you use Cached mode).  And even if he did, it would be back to "normal" within minutes.

If you move the entire store, you're talking about EVERYONE in that store being offline for the entire duration of the move.  Yes, the new store method will likely take longer, but it can be done with far less disruption to your users.
@leew, how u consider the moving for the mailbox will take minutes only, hay guys please take care of your words, I have moved some mailboxes before and some of user took more than hours, it depends on the mailbox size, you can't tell it will take minutes unless u know the size of the mailbox,
waleeda, I have moved more mailboxes than I care to remember, and a small mailbox will take minutes to move.  I suggest you read the comments you are commenting on before you post contradictory remarks.

Either way, moving a single mailbox only effects a single user.  It does not effect all users in a 200GB mailstore, moving a mailstore of this size will take pretty much all day and that means all users without mail for the whole day.

Also, moving the mailboxes to a new store, provides a clean, defragmented, error free mailstore.

Yes I know that moving database it will affect downtime for the whole store but the auther himself asking for moving database that's why I have posted to him the ms article how to move db, also regarding moving mailbox, if u have moved mailboxes more than creating user as u said, the mailbox will be down during the movement, only in exchange 2010 online moving is there, so my concerne that u was telling "no downtime" while there is, and it can be hours not minutes as leew mentioned before, as I mentioned it depends on the size of the mailbox,
It really makes no difference, moving a single mailbox is much less downtime than moving a whole mailstore.

The author asked for moving a database, they may not be aware that they can create a new database and move the date that way.

It's our job as "experts" to advise them of the best possible way to achieve their goals.

creating a new mailstore and moving the mailboxes is better in every single way than moving the entire mailstore.
But he didn't mentioned the goals, how u know that, may be he called u or msg u on ur cell phone :)
The goal is to get the data in the mailstore on to the new storage LUN.

Waleeda, I would suggest you stop posting now.  All you have done is atempt to discredit other expert posts in an attempt to be awarded points for your solution.

My ONLY priority is to ensure the user receives the correct advice as is leew's.
May be leew is ur friend only, no prob, see u in other questions ;)
Hello Everyone, Thanks for all your suggestions.   I did realize that there would be some down time for each individual mailbox while their mailbox was being moved to the new store.  I really like Leews answer because our mail store is really defragemented and it would be very good to have all our mail boxes in a nice new clean database.

Bill


Thank you!!!
That is indeed the correct and best solution.
And to give credit where credit is due - demazter did answer/clarify part of the question with regards to the public folders...
But can we move public folder also as per the below article. Need clarity on this.


http://support.microsoft.com/kb/821915