locked
Exch 2007 Database still large after moving all email boxes AND doing a offline Defrag RRS feed

  • Question

  • Exchange 2007, SP3, RU6.  General question. I migrated all mailboxes out of a database (into another DB), then offlined that particular database and ran a defrag (eseutil /d "mailbox database3.edb").  I've done thise to two other databases we have, and after the fact get reduced to virtually 0 (4 MB to be exact).

    When I did this latest database (was at 123 GB), it defragged down to 10 GB, not exactly what I was expecting.

    Any ideas?

    Thanks,

    James

    Tuesday, July 17, 2012 3:04 PM

Answers

  • On Tue, 17 Jul 2012 15:04:56 +0000, Tandy Brands wrote:
     
    >
    >
    >Exchange 2007, SP3, RU6. General question. I migrated all mailboxes out of a database (into another DB), then offlined that particular database and ran a defrag (eseutil /d "mailbox database3.edb"). I've done thise to two other databases we have, and after the fact get reduced to virtually 0 (4 MB to be exact).
    >
    >When I did this latest database (was at 123 GB), it defragged down to 10 GB, not exactly what I was expecting.
    >
    >Any ideas?
     
    If you're sure there are no mailboxes in that databases (except for
    the one's used by the system) then why bother defragging the database
    at all? Just dismount it and then delete the file and (assuming you
    have only one DB in the Storage Group) the log files and checkpoint
    file. Remounting the database after that will create an empty database
    file. It's a lot faster than running eseutil!
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by emma.yoyo Tuesday, July 24, 2012 1:40 AM
    Tuesday, July 17, 2012 7:42 PM

All replies

  • On Tue, 17 Jul 2012 15:04:56 +0000, Tandy Brands wrote:
     
    >
    >
    >Exchange 2007, SP3, RU6. General question. I migrated all mailboxes out of a database (into another DB), then offlined that particular database and ran a defrag (eseutil /d "mailbox database3.edb"). I've done thise to two other databases we have, and after the fact get reduced to virtually 0 (4 MB to be exact).
    >
    >When I did this latest database (was at 123 GB), it defragged down to 10 GB, not exactly what I was expecting.
    >
    >Any ideas?
     
    If you're sure there are no mailboxes in that databases (except for
    the one's used by the system) then why bother defragging the database
    at all? Just dismount it and then delete the file and (assuming you
    have only one DB in the Storage Group) the log files and checkpoint
    file. Remounting the database after that will create an empty database
    file. It's a lot faster than running eseutil!
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by emma.yoyo Tuesday, July 24, 2012 1:40 AM
    Tuesday, July 17, 2012 7:42 PM
  • Agreed.  By defragging it gave me a sense of nothing was left in it.  So when I ended up doing that, I was quite surprised for it to report 10 GB in it.  the EMC does not show any mailboxes using it.

    The Storage group itself does have two other databases in it.  Again, inherited and not my doing.  I definately subscribe to the One storage group, one DB methodology.

    There are a few sub directories as well in the location where the DB's are located.  they say "catalogdata-a-bunch-of-Hex-numbers.  these would appear to be maybe indexing files?  Just not sure which one would be for which, so not sue which one I can delete.

    Thanks,

    James

    Tuesday, July 17, 2012 10:43 PM
  • On Tue, 17 Jul 2012 22:43:04 +0000, Tandy Brands wrote:
     
    >Agreed. By defragging it gave me a sense of nothing was left in it. So when I ended up doing that, I was quite surprised for it to report 10 GB in it. the EMC does not show any mailboxes using it.
     
    The EMC only shows you "normal" mailboxes. It doesn't show you any
    system mailboxes.
     
    >The Storage group itself does have two other databases in it. Again, inherited and not my doing. I definately subscribe to the One storage group, one DB methodology.
     
    Easy to fix . . . create the additional SGs and move users to a new
    database in the SG. Then remove the old DB and delete the file. When
    you're done there won't be any databases in the directory so you can
    remove all the log files for the SG (and the checkpoint file) and the
    catalogs (they're for full text indexing).
     
    >There are a few sub directories as well in the location where the DB's are located. they say "catalogdata-a-bunch-of-Hex-numbers. these would appear to be maybe indexing files? Just not sure which one would be for which, so not sue which one I can delete.
     
    See above.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Wednesday, July 18, 2012 2:28 AM