Exchange Offline Defragmentation

I have a problem with offline defrag,
My database file size is 84GB.as per event id 1221 we found 47 GB white space but to perform offline defrag we need  110% free space on disk. Now the question is what we have to conceder database size that means 110% of 84GB or 110% of (84 - 47 = 37) GB. Someone help me on this……….
RamRazAsked:
Who is Participating?
 
nitin_badhwarCommented:
Hi RamRaz

You require 110 % of total Database size.
means 110% of 84GB of your Database.
If you do not have another disk to do that, you can attach a external hard drive as well to do this.

if you can elaborate your requirement and also the version of exchange you have this issue, I can think of some safe solution rather the simply defrag.

Event id  1221 can tell you how much free space is available in your database.
http://support.microsoft.com/?kbid=195914 can help you with

Nitin
0
 
Sushil SonawaneCommented:
You required approximately double free space 160 GB.  When defragmentation running that time exchange create a temp database on the server.

When Eseutil defragments a database by eliminating unused storage and compacting the database, Eseutil actually creates a new database that contains all the information from the original database. When defragmentation is complete, the original database is deleted or saved to a user-specified location, and the new version is copied over the original. If the utility encounters a serious logical problem in the database, defragmentation stops. The database must then first be repaired with Eseutil /P before it can be defragmented.

When an offline defragmentation is performed, Exchange makes temporary copies of the database file (.edb file) and the streaming database file (.stm file). Tables from the .edb file are preserved and copied into the temporary database, but empty pages and indexes are discarded. Because this causes physical page numbers in the database to be changed, pages are not copied unaltered; the page links between them are all updated, and all pages left in the database undergo integrity checks. All pages in the .stm file that has information on them are preserved in the temporary .stm file, and references to the pages are updated in the .edb file.

Please refer below link:

(http://technet.microsoft.com/en-us/library/bb123761(v=exchg.65).aspx)

Before going to defragmentation  Please take your exchange database backup.
0
 
Malli BoppeCommented:
I wouldn't reommend you to do a offline defrag.
The better option would be to create new database (provided you have space) and start moving the mailboxes.this way the downtime is minimal.
0
 
lucid8Commented:
Mboppe is on point here in that moving the mailboxes to a new database depending on the version of exchange you are running will only impact the mailboxes being moved and can end up taking less space as well i.e.

1. Turn on circular logging temporarily otherwise you will have some pretty massive log growth.

2. Created database B and move all existing mailboxes from current DB to database B

3. When down turn circular logging off

4. Get a good backup of the new database you just moved everyone into.

5. Dismount the original database

6. Now delete the database file, or if you want to keep it around for safe keeping you can move to an alternate location OR just rename it for now

7. No from Exchange Management tell it to Mount that database that you just deleted/moved/renamed and Exchange will squawk that the DB files are missing and if you continue it will create a new DB file. Say yes and you now have a new clean dial tone DB ready take on new mailboxes.

Once you clean up the old DB files you are done.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.