This is an archive version of the document. To get the most up-to-date information, see the current version.

Required Backup Job Settings

When you create a backup job, make sure to enable the application-aware processing option, as described in the Specify Guest Processing Settings section of the Veeam Backup & Replication User Guide.

Configuring Transaction Logs

For more information about configuring transaction logs, see the Microsoft SQL Server Transaction Log Settings section of the Veeam Backup & Replication User Guide.

Recovery Model

Required Backup Job Settings Note

To be able to restore your data as of a point in time or as of a state before undesired transactions, make sure the recovery model for the database is set to full or bulk-logged.

The following table lists database logging models and applicable Veeam options.

SQL DB Logging Model	Veeam Options
	Truncate logs	Do not truncate logs	Backup logs periodically
Simple	Databases are skipped from processing.	Applicable option.	Databases are skipped from processing. Log files do not grow (and do not need to be backed up).
Full	Applicable option. Veeam performs “backup to NUL” for log files on guest.	Applicable but not recommended to use without native or 3rd party means of log truncation or backup – otherwise, logs will increase in size.	Applicable option. Log backup files (.BAK) are copied from the temporary folder on SQL Server to Veeam repository. As soon as data is copied to target, BAK files are deleted from source.
Bulk-logged	Applicable option. Veeam performs “backup to NUL” for log files on guest.	Applicable but not recommended to use without native or 3rd party means of log truncation or backup – otherwise, logs will increase in size.	Applicable option. Log backup files (.BAK) are copied from the temporary folder on SQL Server to Veeam repository. As soon as data is copied to target, BAK files are deleted from source.