Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!

General discussion


MD Exch Svr 5.5 out of disk space

By hmillican ·
I have Exchange Server 5.5 running on an Intel Redwood MOBO, 2 300Mhz processors, and a SCSI Raid with 69 GB of disk space. Nothing else is on the machine. The available disk space is 9MB. Even after I make the users clean up their mailboxes I still need to execute eseutil to recover my disk space. But, to run eseutil you need at least 25% of the database size to run the utility. Obviously I don't have that much space available. Can anyone point me in the correct direction to resolve this, we currently have no email. BTW: email doesn't work because the MTA, Message Transfer Agent, Can't start.

Thanks to anyone who will offer some avice

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by caestelle In reply to MD Exch Svr 5.5 out of d ...

I don't that this will clear up enough space for you, but give this a try. Try deleting some of the Exchange log files...they can be stored in various locations, so the easieted way to find them would be to search, should have a ".EDB" extension. Once you find them, I would sort by date and delete the older logs and keep atleast the last day or twos. Hope this helps!!

Collapse -

by caestelle In reply to

I just went back and read my suggestion and those that follow and realized after reading rholliday's response that there was a typo\brain fart in my suggestion. The files you want to delete\move(depending on your preference) are edb*.log, where * is a hexadecimal number. You will want to sort them by date and only delete\move the older files. You will need to stop Exchange servces when doing the deleting/moving. To be safe, I would suggest you move the files rather than deleting them. So again, do NOT delete any *.edb files...instead only delete/move edb*.log files.
Sorry for the confusion!!!!

Collapse -

by BP7226 In reply to MD Exch Svr 5.5 out of d ...

You may not like this answer, but I had this problem and went to the Microsoft KnowledgeBase and did what they suggested. It involved copying the database to an external drive and running the eseutil on thaty copy, then copying the database back top the original drive. There are some special steps required to make everything work when you copy it back. If you have difficulty locating all the relevant articles in MS KnowledgeBase, e-mail me and I will go through my files and send you the relevant article numbers. I might add that although it was not a fun exercise, I was able to restore everyone's email and nothing was lost in the process. I hope that helps.

Collapse -

by rholliday In reply to MD Exch Svr 5.5 out of d ...

Please do not follow the earlier advice and delete your .edb files, these ARE your e-mail store!!!!! Log files are with a .log extension!
I do not advise that you delete the log files as they may be needed if there is a problem after running eseutil.
The only safe way for you to resolve your problem is to copy the .edb files to another hard disk or another computer. eseutil then can be run against the copied files safely, and copied back to their oproper location when finished. Even a cheap ide harddisk will suffice and can be easily added to your server. The disk speed will not be the bottleneck as much as cpu when running eseutil. Goodluck, I've been there.

Collapse -

by lcoots In reply to MD Exch Svr 5.5 out of d ...

1) It may be a slightly-expensive proposition, but I would add another SCSI drive. Then run the Exchange Optimizer utility and allow it to move a segment (or more) of the mail system to the new drive. However, the utility may not work if MTA won't start up, but I suspect it's worth trying. You can try the optimizer before adding another drive... if the utility seems to work, then cancel it, pop in another drive and run it again for real.
2) In addition, you can look for service pack files (usually in a folder named I386) and offload them to another drive, network share, etc. to clear space.
3) Twice, in a pinch, I used NT's built-in file compression to compress a drive long enough to run the cleanup, and once enough space was clear, I decompressed the drive again. It takes time but usually works. Right-click a drive, click Properties, check Compress, choose all files and folders, and let it run.
Good luck!

Related Discussions

Related Forums