Every change in Microsoft SQL database is first written as a record to a transaction log file. Periodically, this data is copied to the database itself, and a checkpoint is created, describing which log entries have been written to the database. After the data is copied to the database, the records in the log files are not deleted, and with time can occupy all of the disk space. The Microsoft SQL Log Truncation feature frees up the disk space by deleting the records in the log files that were committed to the database.
You can configure SQL log truncation on the Options step of backup or replication jobs (make sure that the system requirements are met). Once the feature is set up, NAKIVO Backup & Replication will do the following after you run the job:
Log into the VM(s) that you specified in the Options step.
Run scripts to identify Exchange databases and determine which log files are already committed.
If the conditions specified in the Options step are met, delete records in the log files and clean up all temporary files created by the product.