Defrag Exchange 5.5

[R121]

can anyone please tell me how best to defrag my exchange 5.5 information store because it has almost reached its 16 GB limit?

 

[fuego007]

Stop the Information Store service from the services control panel.

From a DOS prompt, run the following command:

eseutil /d /priv

When this is complete, run the same command using /pub in place of /priv.

Restart the IS (and the Internet Mail service, if installed).

 

[fuego007]

I forgot to mention that if you are actually running Exchange 5.5 and not 5.0, that there is no limit to the size of the databases. If this is the case, the size of your databases is limited only by the available space on the hard drive(s).

 

[R121]

fuego007

THANKS for the quick reply. are you sure about the IS size I've got exchange 5.5 standard version it has 16 GB limit I have been told that by M$ because my exchange server went down a while back I had to delete some old mail boxes to get it back up and running. exchange 5.5 enterprise edition has unlimited IS size.


R121

 

[Maruis]

R121
You are 100% correct on your 16Gig limit on the standard version.

Hope this Helps

Maruis
"I sleep at home not on my Job!"

 

[david902]

most defrag programs will make a backup of the database before starting the defrag, so you will need at least 2x disk space 8GB database will need at least 16GB free disk for the defrag to run.

here we ran into alot of problems running defrag, our 6GB database sat on a 8GB partition. ooops...

 

[fuego007]

I should have corrected myself earlier. Yes, the non-enterprise version does have a 16GB limit.

Sorry about that...

 

[TBG]

I'm running Windows 2000 server with Exchange 5.5 SP4. Will running Windows 2000 defrag do the same job or do I need to do the dos prompt examples above. Thanks.

 

[fuego007]

The Windows 2000 defragger (diskeeper) will not defragment the Exchange databases. You must use the command line method outlined above. NOTE: Using the command line defragmentation utility is only recommended if you absolutelymust reclaim the unused space for some reason. The background process will compact the database without reporting any change in the size of the file (as viewed in Explorer or a DOS window). However, Exchange will fill the unused space in the database file before using more disk space. Additionally, use of the eseutil is recommended ONLY by (or at the direction of) experienced persons and not for routine maintenance.

If you insist on performing a manual defrag, ALWAYS perform a backup first.

No lecture intended, just friendly advice from someone who's seen the eseutil get people in trouble.

Bob

 

[TBG]

Thanks Bob, I don't need to do this defrag but thought it would be a good idea for system maintenance and perhaps speed. I will listen to your advice and do it only as a last resort for regaining disk space. Thanks again.

I'm glad that you put that disclaimer is about not doing this unless necessary. No need in taking the risk of tanking the server or data on it Better of safe then sorry.

 

[zoeythecat]

I think this article may explain.

http://support.microsoft.com/default.aspx?scid=kb;en-us;192185

Also, beware if you get an application error after doing a defrag (if the defrag gets interrupted for some reason)

http://support.microsoft.com/default.aspx?scid=kb;en-us;289079