I'm running Exchange 2010 on Server 2008 R2. I run a VSS Full backup nightly. The Exchange database is backed up, but the log files are not deleted. If I reboot the server and then preform a one time backup the log files are deleted.Any suggestions on why the log files are not being deleted after each backup?

The main reason behind log files not getting deleted or purged is that :1. The log files are not is sequence or2. Any log file is missing.But, as you said that the log files are getting deleted after rebooting the server I really would like to know what all event id's getting generated after the backup(when log files are not purging)

I had the same Issue tonight... I solved it by running a Full Backup with Windows Backup (described here: http://www.roland-ehle.de/archives/942) After that I enabled circular loggin. In the EMC at Organisation Configuration -> Mailbox -> Properties of Mailbox Store(priv or / and public) and at the Maintenance tab I enabled it. After that I unmounted and remounted the store... (like the message suggests) I hope this can help someone other to save some hour´s with troubleshooting. *** Technical background: You can configure Exchange to save disk space by enabling circular logging. Circular logging allows Exchange to overwrite transaction log files after the data that the log files contain is committed to the database. However, if circular logging is enabled, you can recover data only up until the last full backup. For example, you can enable circular logging when using Exchange Native Data Protection, in which you don't make backups. Therefore, to prevent log buildup, you need to enable circular logging. In the standard transaction logging that is used by Exchange 2010, each database transaction is written to a log file and then to the database. When a log file reaches one megabyte (MB) in size, it is renamed and a new log file is created. Over time, this results in a set of log files. If Exchange stops unexpectedly, you can recover the transactions by replaying the data from these log files into the database. Circular logging overwrites and reuses the first log file after the data it contains has been written to the database. In Exchange 2010, circular logging is disabled by default. By enabling it, you reduce drive storage space requirements. However, without a complete set of transaction log files, you cannot recover any data more recent than the last full backup. Therefore, in a normal production environment, circular logging is not recommended. For information about how to enable and disable circular logging, see Configure Mailbox Database Properties. Found here: http://technet.microsoft.com/en-us/library/bb331958.aspx Configuration: SCCM 2007 R2 with MDT 2008

James, You can increase disgnostic logging for VSS , exchange writer and Backup . Please navigate to EMC , exchange server object and from properties select idiagnostic logging for Exchange IS /system and should find the above fields,

hi, agree with M4rkus and also you can use DPM2010 to backup your exchange server 2010 organization. it is really usable for exchange and other microsoft services. regards, Mumin CICEK | Exchange - MVP | www.cozumbilisim.com.tr | www.mumincicek.com | www.cozumpark.com

I ran into a very similar problem with pretty much the same exact Exchange10 setup. I was running out of volume space very quickly, and the amount of log files was to large to run a backup fast enough to clear them out before the store was automatically unmounted. Luckily, my Zenoss server reported the volume at 10% capacity before it stopped accepting mail. So here is what you do when you have found this dreaded problem and it takes literally 5 minutes to fix. Just keep in mind you have to undo this fix if you want reliable backups in the future. Open EMC In the Tree click on Organization Configuration to expand it. Click on Mailbox and the Mailbox Database stores will be displayed. Find the Store that is overflowing. D: in my case. Right click and go to "properties" Navigate to the "Maintenance" tab Below you'll find-"Enable Circular Logging" Go ahead and put a check mark next to it. Click Apply Unmount the store Remount the store *POOF* Log files are gone! Downside to this? You can't restore with current data. You can only restore from your last backup. Old log files are overwritten during this procedure and not enabled by default for a reason. I enabled circular logging, backed up the server, and disabled circular logging and scheduled more frequent backups in order to keep the log files under control.

Hello All, Is it safe to move transaction logs files that are about 2 days old to a different destination, if I am running out of disk space ?

The Exchange 2010 backup will truncate those logs. If they are not truncating and you are absolutely sure you are using an Exchange aware application then you need to raise a ticket with the software vendor. What backup package are you using? "olu2006" wrote in message news:e6b101f5-fc34-41cc-b850-7017ddcc0181... Hello All, Is it safe to move transaction logs files that are about 2 days old to a different destination, if I am running out of disk space ? Mark Arnold, Exchange MVP.

Oh my, "My backups are failing to truncate the logs", so I think I'll just; a. Just move a bunch of them somewhere else and punch a big hole in my log file sequence. b. Just turn on circular logging and lose the ability to restore and roll the logs forward (the whole point of taking VSS backups BTW). c. Contact my backup vendor, open a ticket, and figure out why it's not working properly (why it's not clearing the logs after a backup). It's actually shocking to see how many folks have responded with anything other than the correct answer "C" in this thread. J