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

Exchange 2007 Low Disk Space due to Transaction Logs

Hello, everyone.

I just want to preface this with this was a huge oversight on my part and poor planning.

My problem is that i'm running out of diskspace because of exchange log files. My backups were failing for exchange (via Windows Backup) and thus not purging old log files.

I'm running very very low on disk space and I am curious about my options before my stores go offline.

What are some of my options? Can I enable circular logging, have it purge all of the old files, then disable it and resume a normal backup? What is the best practice here?

Thanks so much for your help, seriously.
0
erickemp
Asked:
erickemp
  • 3
  • 2
  • 2
  • +4
2 Solutions
 
davorinCommented:
The best practice is to make backup work properly. But for short time, as you said,  you can enable circular logging to get more space. Sometimes I make use of this temporary solution - like in your case - when costumer has problems with backup and low space or when I'm  moving large number of mailboxes.
0
 
Simon Butler (Sembee)ConsultantCommented:
Just compress the logs.
Don't compress the entire folder or anything newer than an hour old.
Then do a backup. If Windows Backup is failing, then download Backup Assist and use the trial version to backup to something else.

Simon.
0
 
erickempAuthor Commented:
So, what are the consequences of doing this? Am I going to lose anything if I were to enable circular logging?
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
Stelian StanCommented:
Like you and davorin already mentioned the best option at this point is to turn on the circular login till you gain some space and do a FULL backup after.

Another option is to move the Exchange Transport queue database: http://exchangeserverpro.com/exchange-server-2007-event-id-15002-and-431-insufficient-system-resources-errors
0
 
Nagendra Pratap SinghCommented:
Run this in the logs folder

COMPACT /C *.log

sit back for sometime and fix your backup solution in the meanwhile.
0
 
davorinCommented:
In simple words - You have logs building up from your last successful backup. If your database gets corrupted, you can restore it from backup and "play" the existing logs into the database until the very last moment. If you get rid of your transaction logs, then you can restore the database at the time when the last backup was created.
You loose the option to do up-to-date restore if something bad happens to your database.
0
 
LexiLuckyCommented:
One problem with circular logging is you will need to unmount/mount the database before it will take affect.  Compressing the directory will work short term but I would recommend moving them if possible with the link already provided if you have the space available on another drive!
0
 
Simon Butler (Sembee)ConsultantCommented:
The above advice to compress everything in the directory is wrong - and that wasn't what I said to do. As the logs are active, you shouldn't compress anything that is in current use - only compress the old content.

Simon.
0
 
Nagendra Pratap SinghCommented:
Well I did not say everything.

You can modify this to COMPACT /C E0004*.log etc. after checking the file names.
0
 
davorinCommented:
Link is talking about moving transport queue database - it could help if you have transactional logs on the same drive than queue. As already said, you can also change transaction logs path. But I guess you don't have enough space anywhere.

Simon's idea of compressing old logs sounds the best option to me. You don't lose anything and you have no downtime.
0
 
lucid8Commented:
Agreed on compressing all logs older than one hour and then executing a backup is a good plan however if you ever do a recovery with that data set you will need to restore all the data and then decompress the compressed logs.
0
 
erickempAuthor Commented:
Thanks for everything, everyone. I started to compress the logs, and it was working. However,  needing the space in lump-sum. So enabling circular logging, then disabling it, was the more direct approach that was necessary to continue functioning for the day.

I'm going to be working on making sure the backups are properly functioning so I can avoid this whole mess in the future.
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

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