Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1856
  • Last Modified:

Compact mailbox databases online after moving mailboxes

Hi,

I moved about half my mailboxes to another database.  I am running Exchange 2007. I noticed that the first database still shows its original size.  I was interested in not taking the database offline, is there a way to compact it or run maintenace with it online to recapture this free space?  I noticed from what I could find through searches that eseutil was recommended for running offline defragment maintenance jobs for this purpose.  Just trying to confirm or get other ideas.
0
ebwood
Asked:
ebwood
  • 4
  • 3
1 Solution
 
SembeeCommented:
Offline defrag is the only way to get the database to shrink. However that involves total downtime.

With Exchange 2007, I am not actually suggesting it at all. Instead, move ALL the mailboxes to another database then drop the original one. Then create a new one and move them all back. No downtime. Not like Exchange 2003 where standard edition was restricted to one store. With 2007 you can have 4.

Simon.
0
 
ebwoodAuthor Commented:
The only trouble is that we have LCR turned on, so we are a little limited.  I currently have two databases, trying to split the load, so that we don't go past the size 75gb limitation in standard ed.  The first db is at 62gb and it should shrink at least 24gb as that is what I've moved out to the second db at this point.  I had actually seen an article on this same scenario you are suggesting, and may try this method, just looking for confirmation...

Thanks!
0
 
SembeeCommented:
I would suggest that you read up on Exchange 2007 a bit more. If your only reason for moving data around is to avoid the limit then you are mistaken. There is no limit on database sizes in Exchange 2007 (well there is - about 20tb)

Simon.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
ebwoodAuthor Commented:
Actually I did see that it is set to 16tb, but I can tell you for certain, that at 50gb with Standard Ed, that we started having issues.  I found a registry entry that allowed us to raise the limit to 75gb, and after implementing that the clients worked properly.  I also know from my research that SP1 is supposed to raise the default limit to 150gb.  I from what I can tell theoretically and possibly with the Enterprise ed. you could go to 16tb.  
0
 
SembeeCommented:
There is a soft limit in Exchange 2007, to stop things from running away, but it is not a hard limit like the 75gb limit in Exchange 2003.

If you are seeing issues with Exchange over 50gb then you need to look at how you are managing your Exchange servers. I have managed databases three times that size with no problems. The 50gb number is the usual number for ease of disaster recovery, but has nothing to do with performance.

The 16tb limit is always theoretical, simply because of the demands it makes on storage.

Simon.
0
 
ebwoodAuthor Commented:
I am running LCR on the db's, could that have anything to do with the limit that I hit?  Just curious now...
0
 
SembeeCommented:
I am not aware of any issues with LCR regarding size.

Simon.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now