Hello, My transaction logs aren't purging after a full backup. Are there any risk if I were to delete the transaction logs manually? Thanks in advance,

It's not recommended. The main risk is that you will lose the ability to recover the database up-to-the-minute in the event of a failure. You're also going to run into trouble I suspect if you delete any of the special logs (i.e. res*). Rather than manually delete the logs, enable circular logging temporarily and then disable it again when the logs have cleared. You still lose the ability to recover up-to-the-minute, but at least it will clear the logs cleanly. You can do this in Exchange 2010 while the database is running, e.g. Set-MailboxDatabase DB1 -CircularloggingEnabled:$true and then Set-MailboxDatabase DB1 -CircularloggingEnabled:$falseTony www.activedir.org blog:www.open-a-socket.com

In general, if you delete the logs and exchange database get corrupted then you cannot repair the database in the soft repair or try to mount the database because the database requires the verify and replay the logs to make sure everything is correct. I would suggest to look into why the backup did not purge the logs before deleting the logs else you can remap the log location to a bigger drive.

The problem was the logs haven't been cleared in a year and a half and I'm running out of space, so I manually deleted the logs up until yesterday. I noticed there is an EventID 200 that says "Instance 2: Database headers have been successfully validated. All databases are in a dirty shutdown state. To bring these databases to a clean shutdown state, log generations 7526 (0x00001d66) to 7527 (0x00001d67) will be required" I think this could be the cause - yes?

What are you using to backup Exchange? There should be an option to purge the logs. It's because you are running out of space that is why it is generating the message.

I'm backing up with BackupExec 2010. However, even though it is set to clear the logs after full backup, it doesn't.