User guide

205 Copyright © Acronis International GmbH, 2002-2012
3. In the Post-backup command, specify the path to the batch file.
11.1.2.2 Transaction log truncation for Exchange Server
Before committing a transaction to a database file, Exchange logs it to a transaction log file. To track
which of the logged transactions have been committed to the database, Exchange uses checkpoint
files. Once the transactions are committed to the database and tracked by the checkpoint files, the
log files are no longer needed by the database.
If log files are not deleted, they will eventually consume all the available disk space and the Exchange
databases will be taken offline until the log files are purged from the disk. Using circular logging is not
a best practice for a production environment. When circular logging is enabled, Exchange overwrites
the first log file after its data has been committed to the database, and you can recover data only up
until the last backup.
We recommend that you delete the log files after backing up an Exchange server, because log files
are backed up along with other files. Therefore, after a recovery you will be able to roll the database
back or forward.
For more information about transaction logging see
http://technet.microsoft.com/en-us/library/bb331958.aspx.
Log truncation of offline databases
This is the easiest way of deleting log files. After normal shutdown the database state is considered
consistent and the database files are self-contained. This means that you can delete all the log files of
the database or the storage group.
To delete transaction log files:
1. Dismount the database (in Exchange 2010) or all databases of the storage group (in Exchange
2003/2007). For more information, see:
 Exchange 2010: http://technet.microsoft.com/en-us/library/bb123903
 Exchange 2007: http://technet.microsoft.com/en-us/library/bb124936(v=exchg.80)
 Exchange 2003: http://technet.microsoft.com/en-us/library/aa996179(v=exchg.65)
2. Delete all the log files of the database or the storage group.
3. Mount the dismounted database or databases.
For more information, see:
 Exchange 2010: http://technet.microsoft.com/en-us/library/bb123587.aspx
 Exchange 2007: http://technet.microsoft.com/en-us/library/aa998871(v=exchg.80).aspx
 Exchange 2003: http://technet.microsoft.com/en-us/library/aa995829(v=exchg.65)
Log truncation of online databases
This method is good for the databases that are in constant use and cannot be dismounted. If a
database is in use, you can safely delete only those transaction log files whose data has been
committed to the database. Do not delete log files whose data has not been committed to the
database, they are essential to recover the database consistency from unexpected shutdown.
To delete the committed transaction logs
1. Determine which logs have been committed to the database by using the Eseutil tool: