Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Slowly running out of space on Exchange Server C: Drive 1

Status
Not open for further replies.

njang177

IS-IT--Management
Apr 27, 2001
5
0
0
US
Can anybody help me out here? I am starting to lose space on my C:\ of my exchange server 5.5. I only have about 411 mb of space left, and I am afraid that I might use that up pretty soon.

I am running exchange server 5.5 with sp3. I have two drives:

C:\ = used = 1.60 GB free = 406 mb
D:\ = used = 1.58 GB free = 4.82 GB

I don't want this machine to crash or stop due to lack of space, however; how do I free up space on the root directory of this machine and prevent that from happening?

I ever went as far as deleting everything from the root directory that was not needed on the machine. Can anyone give me some suggestions? I look forward to your reply's.

Thanks
Bob
 
Run Performance Optimizer, and let it move things around for you.
 
There are two possible sources for all this data. One is the logging you have set up. Make sure that the logging level is set to none throughout.

The second possible data source is Exchange's internal housekeeping files. These will only be removed by Exchange when they have been backed up by Exchange-aware backup software such as Backup Exec with the Exchange component.

Hope this helps

Peter
 
Thank you for your imput.

I have checked on both of these issues that you make mention too, and I don't have logging enabled anywhere in the exchange environment. And, as far as the backups are concerned, I have all logs being flushed and or (committed) after the Backup Exec completes its back-up.

Are there possibly any other logs and or data files that exchange places in the root directory that can be moved to the other drive (where the space is ample)? Or, can any logs be deleted to conserve this precious space on the root (C:\) directory.

Bob
 
Run the exchange optimizer from your echange server this will allow you to move exchange to the D: drive.
Please not that the optimiser will shut down mail while it runs.

Michaël J. H. Warnon
Senior Network Support Specialist
Information Services
Email: mwarnon@co.orange.ny.us
 
You might want to run a file search by date and see whats changed, what about the swap file size ? if you have the dB's and log's on C: move them to D:

 
Also concerning your backup check to see if circular logging is enabled. If you are doing backups uncheck it. This should help in the size of the log files. Mantislee
Systems Administrator
mantislee@yahoo.com
 
Look for your MTADATA folder and determine the number of .dat files located in that folder. When messages are sent these files will not be removed but their size will not be an issue. A message may be corrupt and each time there is an attempt to send it it causes an increase in the amount of disk space used. Do an mtacheck /v on this server. This will find and remove any corrupt messages you may have. Run the mtacheck /v again until zero messages were found to be corrupt.
 
Try checking the PRIV.EDB file. This is the private information store and can be found in c:\exchsrvr\mdbdata I had a similar problem where my C: drive ran out of space and it was due to an extremely large Priv.edb file (almost 4gb. I ran the defragmentation routine using the eseutil.exe utility (see microsoft support website search.support.microsoft.com and search for "How to defragment using the eseutil utility (eseutil.exe)"
Running the routine on my exchange 5.5 server reduced the file from 4gb to 400mb! freeing up over 3.5gb.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top