When you create a new backup job, make sure you enable the application-aware image processing option and specify required application-specific settings to be able to explore and recover your data using Veeam Explorer.
For more information about application-aware image processing, see 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 Transaction Log Settings: Microsoft SQL Server section of the Veeam Backup & Replication User Guide.
Recovery Model
|
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. |
