Microsoft Exchange is the industry's leading platform for e-mail, calendaring, and messaging. NAKIVO Backup & Replication can create consistent backups as well as truncate transaction log files of Microsoft Exchange 2007, 2010, 2013, and 2016 servers. The transaction logs record all changes that are made to an Exchange Server database. Over time, these log files accumulate and can consume all of the available disk space, if not periodically removed.
Here’s how Microsoft Exchange Log Truncation works. Every change in a Microsoft Exchange database is first written to a memory buffer and a transaction log file. Periodically, this data is flushed to the actual database file and a checkpoint is created, describing which transaction log entries have been written to the database. If your server that runs Microsoft Exchange crashes or shuts down ungracefully, the information that was written to the memory/log files is not available in the database after the server restart. To prevent data loss, the Exchange database comes online in the "dirty shutdown" state and, using the checkpoint information, enables you to replay transaction log files to recover the information.
Since your Microsoft Exchange database will be constantly changing (as new data is written to and old data is removed from the database), the transaction logs will grow and grow over time, and will eventually fill up the disk, if they are not removed. In order to remove the transaction log files, the database needs to be backed up.
After creating a successful backup, NAKIVO Backup & Replication connects to your Exchange server, identifies which transaction log files have already been written to the database and removes (aka truncates) those log files.
As a result, NAKIVO Backup & Replication creates regular, application-consistent backups of your Exchange server and also removes the transaction log files so they don’t consume all free disk space on the server.