How To Remove Exchange Server 2010 Transaction Log Files
Another possibility is to judiciously remove unneeded Exchange transaction logs. Although Microsoft doesn't recommend it, there is a way to find out manually which transaction logs are no longer needed by determining the last checkpoint created by an Exchange Server backup. Exchange Server 2010 customers sometimes ask why their server disk drive is filling up with log files. Usually they are referring to the transaction log files created by the mailbox databases. Update February 2013 – there is a specific issue with iOS 6.1 that causes excessive log generation on Exchange servers. Click here for more details. How to manually purge Exchange server logs – clean and easy Update 9/Jun/2015 – Thanks to Josh Davis for the feedback, I’ve added a note about making sure to include both drives (if EDB and LOG files are separated).
Exchange Server 2010 Release Date
While importing mail boxes from *.pst files into an Exchange 2010 database, the transaction logs filled up the C: drive. This caused the database to dismount. The mailbox database is on an E: drive. To free up space and allow the remaining mailboxes to import, I relocated the transaction logs to the E: drive as well. I figured that I could now run a 2008 VSS full copy of Exchange to backup the transaction logs and reduce their size. It backed up but gave me an error about failing the consistency check and didn't reduce the transaction log files. Can I dismount the database, kill the existing transaction log data and then re-point the transaction logs back to the C: drive to start over? This is a new install and just now coming into production. I know this will impact my recover options.Thanks.