exchange server running out of hard drive space

[ralphtg]

Hi

i have an exchange server that up until yesterday seemed ok with space but i never really checked before. Now i was down to 25 MB on my C drive and the MDBDATA folder had a bunch of log files that were 5MB each. I am not sure if I need these log files for anything. So far what I read that whats needed is the res1 and res2 log files and the e00.chk file. But the rest of the log files are all named E00****.log, also the date of the first log is july 17 2005 so this just started to happen recently. any helpfull info would be greatly appreciated.

Thanks,
Ralph

 

[jpm121]

If you're running an Exchange-aware backup program it should be keeping the logs cleared up. How much space total are the logs taking up?

 

[Xanaxo]

The safest way is to perform an immediate full backup using NTBACKUP (or whatever exchange aware backup software you use). Choose an alternate location to backup your data to and it will clean the drive up for you. I highly recommend you try this first.

If you are not running backups, you can enable "Circular Logging" on the Storage group properties. This will keep it circulating through 5 log files. Be aware that by doing this your are limiting your log replay abilities and will most likely lose data in a severe disaster recovery situation.

If you need to clear the space immediately, do the following.

1. Stop the information Store service.
2. Check the state of the databases to make sure they are in a "clean shutdown" state. To do this, use the Exchange utility in the exchsrvr\bin folder called ESEUTIL. The command line is: "ESEUTIL /mh c:\program files\exchsrvr\priv1.edb"

(the "s in the path are required. These are default paths I have specified so if you have changed the location or name of the database alter this syntax accordingly.)

3. Verify the State is Clean shutdown in the output provided.
4. If it is clean shutdown, you may move everything in the MDBDATA folder EXCEPT the .edb and .stm (these are your databases) files to a backup location.
5. Restart the IS service and make sure your databases mount.
6. Once you are sure they have mounted and all is working, you can delete the log files permanently.

If you are unable to start or stop the IS because the drive is full, or perhaps you checked the state of the database and it says "Dirty Shutdown", then please follow the following queue article to remove only a few commited log files long enough to create enough space on your machine to start and then stop the IS to then go back and do the action plan provided above.

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

This applies to 5.5 but should be the same with regard to Exchange2003. Just ignore the DSADATA information.




Steven Parent [MSFT]

 

[ralphtg]

thank you for your answers.
amazingly this started to happen as soon as the tape back up was down so there must be some connection.
we use backup exec 9.1 if I got the backup running again would the server clear the log files or would i have to do that myself.
Thanks,
Ralph

 

[SeanAIX430]

Backup-Exec will clear the logfiles for you

 

[ralphtg]

thank you