IMHO - the answer to that depends on your backup and SLA for
recoverability.  

 

Moving large mailboxes creates a lot of transaction logs.  

 

You might want to consider increasing the amount of space you have
allocated for the transaction logs temporarily while you're doing the
mailbox moves, then cut it back when you're finished.

 

Transaction logs also compress pretty well, so you might consider
enabling compression on the transaction log directories if you can
afford the processor load without it hurting your performance too much.

 

 

 

________________________________

From: Karsten, Matthew [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 29, 2008 12:59 PM
To: MS-Exchange Admin Issues
Subject: Moving Mailboxes

 

Exchange Server 2003 SP2.

 

We have always had all of our users (around 1200) in one large store.
This single store had grown to be around 400GB.  

 

A while ago we decided to start moving all of our users out of this
store and into several different stores organized based on desired
configuration.  We then began moving mailboxes out of the large store in
groups into the other stores.  This has been going fine for our smaller
users.  We now have hit a point where we are at our users that have
larger mailboxes (200mb - 2gb).  As I am moving them in groups, the
stores keep dismounting.  Looking at the event logs it appears that they
are dismounting because the logs are filling up.  

 

I did more looking and it appears that the easiest way to fix this is to
enable circular logging.  Reading more on circular logging, there seem
to be mixed opinions on whether it should be enabled or not.

 

So I guess I have 2 questions.  

1.  Is circular logging the way to go to deal with this?

2.  If so, is there anything I need to watch out for?

 

I had been planning just to enable it to finish the mailbox moves and
then just turn it off.

 

Matt Karsten

 

 

**************************************************************************************************
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
**************************************************************************************************

~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to