Required Job Settings

When you create backup jobs, replication jobs, and CDP policies, make sure to enable application-aware processing in the Veeam Backup & Replication console:

When you configure a backup job, you can do this at the Specify Guest Processing Settings step of the New Backup Job wizard.
When you configure a replication job, you can do this at the Specify Guest Processing Settings step of the New Replication Job wizard.
When you configure a CDP policy, you can do this at the Specify Guest Processing Settings step of the New CDP Policy wizard.

Without application-aware processing, the created restore points will be crash-consistent only.

Veeam Explorer for Microsoft SQL Server allows you to explore crash-consistent restore points with heuristic analysis, which scans the restore point for application data. Note that application item restore from crash-consistent restore points is less reliable than restore from application-consistent restore points. Without application-aware processing, the restore point could contain unfinished database transactions or incomplete application files, which may affect data recovery.

Consider the following:

For backups made with Veeam Backup for OLVM and RHV and Veeam Backup for Proxmox VE, application-aware processing is not supported.
For VeeamZIP backups, application-aware processing is not supported. For more information, see the VeeamZIP section of the Veeam Backup & Replication User Guide.
For storage snapshots, application-aware processing is automatically enabled. For more information, see the Application Item Restore from Storage Snapshots 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. Note that backups of transaction logs are only available for backup jobs created by Veeam Backup & Replication.

Recovery Model

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 options in Veeam Backup & Replication.

SQL DB Logging Model	Veeam Backup & Replication 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 Backup & Replication 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 (in the BAK format) are copied from the temporary folder on the Microsoft SQL Server to a backup repository. As soon as the data is copied to the target, BAK files are deleted from the source.
Bulk-logged	Applicable option. Veeam Backup & Replication 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 (in the BAK format) are copied from the temporary folder on the Microsoft SQL Server to a backup repository. As soon as the data is copied to the target, BAK files are deleted from the source.