I have Exchange 2007 running on 2003 R2 x64. BackupExec 11d for backups. I have LCR on the first storage group. Circular logging is not enabled. For the last 6 weeks or so backups of this storage group haven't been deleting the transaction logs and I'm fast running out of disk space. Can anyone tell me why the transaction logs are failing to be purged? Mailbox database properties is showing successful backup was on 17th November even though I've had numerous successful full backups of the first storage group with Backup Exec since that date! I know I could disable LCR and get a tranche of disk space back but I'd prefer not to do this as the database is over the 100Gb that Microsoft recommend for a database without LCR.

I would suggest running a backup using the built in backup tool to begin with. See what happens then. Run the best practises analyser from the Toolbox as well, and see what that reports. It is possible to manually flush the log files, you have to do some work on the database to verify what is required or not. However that doesn't fix the underlying problem. Is anything logged after the backup is completed? Have you checked the permissions are correct on the log file location? I recall looking at a server once where the permissions were screwed up and the logs couldn't be deleted. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

Hi Simon and thanks for your suggestions, I ran an NT backup on the mailstore last night - or at least I tried - the event log reported "Backup failed because the storage group is already in the process of being backed up." even though no backups were in progress (unless I'm missing something here) - could this be a clue? I also checked the event log at the time of the last successful (according to BackupExec) backup and a similiar theme crops up: "An attempt to prepare the storage group '1. First Storage Group - (Current Staff)' for backup failed because the storage group is already in the process of being backed up. The error code is 1293." Looks like my successful backup wasn't so successful after all - a bit dishonest of BE to report otherwise I think. Best practices analyser doesn't mention anything relevent, and permissions are fine. Richard

Reboot the server should release the database backup setting. You should then be able to do a successful backup using NT Backup, which will flush the logs. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

I'll do a reboot tonight. Interestingly, backups on Storage Groups 2 and 3 flush the logs fine so it only SG1 that's got "stuck". RichardRichard Thomas, IT Manager EHEL

Thanks for your help with this Simon. Following reboot and backup, the transaction logs have flushed and I've got some disk space back! All the best RichardRichard Thomas, IT Manager EHEL

I would do an NT back as well as ensure that the online maintenance is running properly.

I would do an NT back as well as ensure that the online maintenance is running properly.