Hi, I see a lot of posts about logs not being purged, but I have the opposite problem! We have two backup products backing up Exchange 2010 (dont ask, out of my control!). One backs up the database and log drive and one backs up the system drive only. The problem is that hte system drive backups are causing the logs to commit and Exchange 2010 reports the database has been backed up when it clearly hasnt. Does anyone know how Exchange 2010 decides on whether it has been backed up or not? Why would a C: drive backup cause the databases held on D: and logs on E: to think they have been backed up? I am waiting to hear back from the vendor to see if their application is "system aware" and is causing the logs to think they are backed up, but would like to know how Exchange knows it has been backed up - ie does it look for an archive bit, etc on the edb files? Thanks

Can you check the job and verify to see it touches any of the Exch volumes at all? Are the logs on the system drive?Sukh

Can you check the job and verify to see it touches any of the Exch volumes at all? Are the logs on the system drive?Sukh

I have found the problem. We use Veeam for backing up the VM system drives. By default Veeam truncates logs when its job completes even if the job isnt set to backup the databases. I have disabled this setting after hearing back from their support guys.