• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 37
  • Last Modified:

Exchange log filled up disk

It looks like the disk being too full knocked my mail store offline. I am trying to run "C:\Program Files\exchsrvr\bin\eseutil.exe" /MH "D:\mdbdata\Mb1.edb" to see which log files I can get rid. seem to be tons of them. However when I run this utility I am getting this error

operation terminated with error  -1023 (JET_errInvalidPath, Ivalid file path.)

What can I do to resolve this and get the database up again ASAP?

Thanks.
0
raffie613
Asked:
raffie613
  • 7
  • 7
  • 2
1 Solution
 
Will SzymkowskiSenior Solution ArchitectCommented:
What are you using for this machine? Quickest fix would be increase the disk size on the volume and expand the disk in Windows Disk Management.

Another thing you can do is just move the logs to another location and then perform a backup of the database when it is online. Logs are only required if you want to reply them into the database. At this point they have already been written to the database.

Will.
0
 
raffie613Author Commented:
Will,
These are the logs that sit with the .mdb files, not the exchange program logs. I thought someone of them are needed for the exchange mail store to be mountable? I was trying to determine which ones I can remove.

Thanks.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
There should be a check point value in the location what is it? Depending on the check point value, this means that the logs files have been committed to the database which means you can delete anything prior to this safely.

Will.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
raffie613Author Commented:
Check point value? Where do i find that? I am looking in the folder where the logs are. They are all the same size which is 5120 KB
names are all similar like E001E7c4.log
Attributes are the letter A
0
 
Guy LidbetterCommented:
The letter A Is an archive bit value, just means it hasn't been backed up.
Look for a file called E00.chk in the directory, anything before that files time stamp can be safely moved.
0
 
raffie613Author Commented:
ok, Looks like there are several of these type log files being created daily which is causing the drive with the database to get filled up. How do I find out What is casing this?



Thanks.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Take a look at the following link which outlines the type of files you will find in the logs folder.
https://technet.microsoft.com/en-us/library/bb124452%28v=exchg.65%29.aspx

Will.
0
 
raffie613Author Commented:
but how do i determine the what is causing so many logs to be generated? And is there a way to automatically clean them up?

Thanks.
0
 
Guy LidbetterCommented:
The logs are generated by sending\recieving emails, moving mailboxes... anything that might change the database. The log is created prior to committing the changes to a database, this is so that you are not trying to write to it while its busy... its kind of a queue of next actions. The log is kept in case you have a database failure, in which case you can go to your last backup then roll up the logs that are there to get back up to date.
Unless the database is in a circular logging mode, i.e. it doesn't keep logs once the transaction is committed, in this case you will only ever really have one log file. Not a suggested practice...

When a full or incremental backup is taken, all the logs are truncated, that is to say "removed".
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
but how do i determine the what is causing so many logs to be generated? And is there a way to automatically clean them up?

If you are not properly backing up your Exchange database the logs will continue to grow. Logs are only important in the event of a database failure as i have mentioned in my previous comments. The log is written and then committed to the database. At this time the log is not needed any longer which is why the get truncated after a full backup.

As i stated already you can go ahead and either expand the disk or move the logs to another drive. Once you have done this mount your databases and take a Full Backup of the database. After that backup  those log files are no longer useful.

Will.
0
 
raffie613Author Commented:
I am using windows backup to back up the email store database. Should i be doing something else?
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
0
 
raffie613Author Commented:
but it definitely seems like these logs have just started showing up since I started backing up the mail store with NT backup. are these many log files normal to get?
Am I just stuck manually having to clean up these logs every so often?


Thanks.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
How often are you backup up your Exchange server? Also how much mail are you getting? How much maintenace do you do on your databases? All of these things generate logs because you are changing something within the database so a log is generated.

If you find that your logs are building up doing nightly backups will truncate them and reduce the space on your drive.

Will.
0
 
raffie613Author Commented:
I am doing nightly backups. they are still generating.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
If you are backing up Exchange and the logs are not being truncated then the backup is running/configured properly. Aside from that, that is all you need to do.

Will.
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.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 7
  • 7
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now