Hi Martin,

Try backing up the exchange 2007 with windows own backup software, if that purges the transaction logs then backup throgh Backup exec and check if the logs are getting purged or not.

If the windows backup software also could not purge the transaction logs, then you may have to contact MS exchange support for further troubleshooting.

Regards,
tech29

Hello,

Backup Exec never purges the logs, it marks the Logs for deletion. The purging is done by the Daily Maintanance process carried by Exchange Server.

This MS document might help:
http://support.microsoft.com/kb/240145

It actually commits the logs to the DB...I assume that is what you mean when you say it isn't purging them...? Your logs never get cleared?
Anyway, 2 ways of doing this...

1. remove Advanced Open File Option - snapshotting of databases is not supported by Symantec, and it does cause issues like logs not getting cleared. This will then mean that any open data files are going to cause your job to either end up as Completed with Exceptions, or Failed.

2. Look at splitting your jobs: Exchange running first, followed by another backing up data etc. You can do that according to...

https://www-secure.symantec.com/connect/articles/b...

Laters!

@CraigV

I think, its Exchange Server 2007, so it will by default use VSS (Snapshot) based backups....whether we enable it or not.....

Hi again,

2 tech articles for you to read up on:

http://seer.entsupport.symantec.com/docs/340865.htm <-- Best practices for the Exchange agent in BEWS 2010

http://seer.entsupport.symantec.com/docs/299857.htm <-- backing up Exchange using BEWS 2010

Laters!

Hi Martin,

Any news here...?