User manual

199 Copyright © Acronis International GmbH, 2002-2016
 Back up transaction logs by using the native backup engine of Microsoft SQL Server. A database
can be recovered to any point in time by applying transaction logs after a recovery from a backup
created by Acronis Backup.
In both cases, transaction logs will be truncated automatically.
To switch the database to the Simple Recovery Model
1. Run Microsoft SQL Server Management Studio and connect to the instance.
2. Right-click the database, and then click Properties. This will open the Database Properties dialog
box.
3. In the Select a page pane, click Options.
4. In the Recovery Model list, click Simple.
To back up transaction logs by using Transact-SQL
Refer to the following article:
https://technet.microsoft.com/en-US/library/ms186865(v=sql.90).aspx.
11.1.2.2 Transaction log truncation for Exchange Server
About Microsoft Exchange Server log
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 by using the Enable VSS Full backup option
The easiest method of log truncation is to use the Enable VSS Full backup (p. 97) backup option
(Options > Default backup and recovery options > Default backup options > Volume Shadow Copy
Service > Enable VSS Full backup). It is recommended in most cases.
If enabling this option is undesirable (for example, you need to keep logs of another VSS-aware
application running on the machine), follow the recommendations below.
Log truncation of offline databases
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: