Transaction Logs Growing...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I currently have an exchange 2007sp1 server.

I have all of my logs on a seperate volume.

Every night a full backup is performed on all storage groups using symantec
backup exec version 12.

I am wondering since my log volume is growing and running out of space, what
are my options here?

I've heard you can manually delete ones that are not needed and I've also
seen "circular" logging, but I read it was not recommended for a production
environment because of restores etc.
.



Relevant Pages

  • RE: Performance Report & backup log
    ... I am glad to know the report is correct now after you delete the backup ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... <<Server\Support\Backup Logs ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange log files growing
    ... I didn't want to mention the capacity issue until the exchange log issue was ... backup with the excluded data may exceed the cost of biting the bullet now. ... Les Connor [SBS Community Member - SBS MVP] ... I also dig out other old logs when I touch a server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Logs not flushing
    ... Definitely doing a full backup each night (flush committed logs). ... Information Store NGS Storage Group: Beginning the backup of the file ...
    (microsoft.public.exchange.admin)
  • Re: Exchange log files growing
    ... Personally i would delete all the logs from 3/10 and 4/10. ... What do you think about the B/U Exec for SBS? ... Is it inferior to SBS Backup? ... the Exchange log files are growing (over 300 log files in the MDBData ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Server Error 9175
    ... I have a backup solution back in place now and the logs are clearing now as ... You need to start by solving the backup issue. ... A full backup of the exchange information store with an exchange aware ...
    (microsoft.public.exchange.admin)