Veeam Home | Support | Downloads
Veeam Backup & Replication 8.0 for Hyper-V

Veeam Backup & Replication Help Center  > User Guide >  Administration > Creating Backup Jobs > Step 9. Enable Application-Aware Image Processing and Indexing > Transaction Log Settings: Microsoft SQL

Transaction Log Settings: Microsoft SQL

Previous page Next page Print this Topic

Table of contents

If you back up a Microsoft SQL VM, you can specify how Veeam Backup & Replication must handle transaction logs:

1.Select the Enable application-aware image processing check box.
2.Click Applications.
3.In the displayed list, select the necessary VM and click Edit.
4.In the VM Processing Settings window, click the SQL tab.
5.Specify how transaction logs must be handled. Veeam Backup & Replication supports the following options:
Truncate logs (prevent logs from growing forever) — with this option selected, Veeam Backup & Replication runtime process responsible for coordination of application-aware activities will wait for the backup to complete, and then it will trigger truncation of transaction logs. If truncation of transaction logs is not possible for some reason, the logs will remain untouched in the VM guest OS until the next start of the Veeam runtime process.

If selected, this option will allow you to restore your database to the specified restore point only; restore to the certain point in time or to the state prior to specific transaction will not be possible.

Do not truncate logs (requires simple recovery model) —  with this option selected, Veeam Backup & Replication will not trigger transaction log truncation. You will be able to restore a VM from a backup file and apply transaction logs to get the database system to a necessary point in time, even between restore points created by backup job. This option should be used for SQL server databases with simple logging and recovery model (if used in combination with other models, it can lead to immense transaction log size.)

With this option selected, Veeam Backup & Replication will create a VSS snapshot and modify the backup chain (unlike the Copy-Only backup).

Backup logs periodically. With this option selected, Veeam Backup & Replication will periodically ship transaction logs to the backup repository and store them with the SQL server VM backup. Log truncation will still occur during the normal job run.

This backup option will allow you to use any restore scenario: to the state as of VM restore point, to the certain point in time, or to the state prior to specific transaction. In this case, you can also specify how often Veeam Backup & Replication will process these transaction logs, uploading them to repository, set the retention and specify preferred log shipping server for data transfer.

The process of transaction log shipment is described in the How SQL Server Logs Backup Works section.

If you have selected to back up Microsoft SQL transaction logs with Veeam Backup & Replication, you must specify settings for the transaction logs shipment process:

1.In the Backup logs every <period> field, specify the frequency for transaction logs backup. By default, transaction logs are backed up every 15 minutes. The maximum log backup interval is 60 minutes.
2.In the Retain logs section, specify retention policy for transaction logs stored in the backup repository.
Select According to the corresponding image-level backup if you want the same retention policy to be applied to VM backup files and transaction log files.
Select Keep only last <n> days if you want to keep transaction logs for a different period. By default, transaction logs are kept for 15 days. Make sure retention set for transaction logs is not greater than retention set for the VM backup files. It makes no sense to keep logs without keeping restore points to which transaction logs are related.
3.In the Log shipping servers section, specify which log shipping server must be used to process transaction logs.
If you choose Automatic selection, Veeam Backup & Replication will select an optimal shipping server from all available Microsoft Windows hosts added to Veeam Backup & Replication. If an optimal shipping server is busy, Veeam Backup & Replication will direct data flow to another shipping server, not to lose data and to comply with RPO. The process of transaction logs shipment does not require a dedicated server so Veeam Backup & Replication can use any Microsoft Windows server added to the backup infrastructure as a log shipping server.
If you choose Use the specified servers only, you can explicitly define what shipping servers must be used for transaction logs shipping. The server list includes all Microsoft Windows servers added to the backup infrastructure. Make sure that you select a Microsoft Windows server that is not engaged for other resource-consuming tasks. For example, you may want not to use a server that performs the WAN accelerator role as a log shipping server.

For load balance and high availability purposes, it is recommended that you select at least 2 Microsoft Windows hosts for log transfer to act as log shipping servers.

Log shipping servers are assigned per job session. Each time an SQL backup job session restarts, Microsoft Windows servers are re-detected anew.



Veeam Backup & Replication automatically excludes its configuration database from application-aware image processing during backup. As a result, transaction logs for the Veeam Backup & Replication database are not backed up.


Table of contents