You can view the statistics of the transaction log backup job in the History view or in the Home view in Veeam Backup & Replication.
In the statistics window, you can examine the overall statistics for the transaction log backup job, as well as view per-VM information.
In the upper part of the statistics window, Veeam Backup & Replication displays information about the transaction log backup job for all VMs included in the parent backup job.
The Last period (all VMs) section contains statistics data for the selected session of the backup job.
In the Databases column, you can view the following information:
- Protected — number of databases that were backed up at least once during the last session
- Unprotected — number of databases that failed to be backed up during the last session
- Excluded — databases excluded from processing. Databases may be excluded for the following reasons: database status is Offline, database recovery model is set to Simple, database is read-only, database was deleted after the latest full backup, database is added to the list of exclusions, AutoClose property is enabled. For more information, see https://www.veeam.com/kb1051, https://www.veeam.com/kb2110 and https://www.veeam.com/kb2104.
Unprotected databases do not comprise Excluded databases, as they have different reasons for being non-processed.
In the RPO column, you can view the following information:
- SLA value — how many log backup intervals completed in time with successful log backup (calculated as percentage of total number of intervals).
- Misses — how many intervals were missed (number of intervals).
- Max delay — difference between the configured log backup interval and time actually required for log backup. If exceeded, a warning is issued.
In the Status column, the following information is displayed (per job): number of VMs processed successfully, with warnings or with errors.
The Latest session section displays the following information for the latest log processing interval for the selected VM:
- Duration — duration of log shipment from the VM guest OS to the backup repository since the current log processing interval has started
- Bottleneck — operation with the greatest duration in the last completed interval. The operation may have the following bottlenecks:
Saving BAK files to a temporary location on VM guest OS
Uploading log files to the log shipping server
Saving files to the target repository
- Read — amount of data read from the temporary folder on VM guest OS
- Transferred — amount of data transferred to the target repository
The Last period section displays the following statistics of log backups per VM for the latest session of the transaction log backup job:
- The RPO column displays statistics on log processing interval (calculated as described above)
- The Sessions column includes statistics of log backups per VM, calculated as follows:
- Success — number of intervals when all database logs were backed up successfully
- Warning — number of sequential intervals with failed log processing (if not more than 4 intervals in a sequence)
- Errors — number of sequential intervals with failed log processing (more than 4 intervals in a sequence)
- The Duration column includes the following information:
- Average — average duration of log data transfer (through all intervals in the session)
- Max — maximal duration of log data transfer (through all intervals in the session)
- Sync interval — duration of periodic intervals specified for log backup in the parent job settings (default is 15 min)
- The Log size column displays the following information:
- Average — average amount of data read from the VM guest OS through all intervals
- Max — maximal amount of data read from the VM guest OS over all 15-min intervals
- Total — total amount of data written to the backup repository
Statistics on transaction log processing is updated periodically, simultaneously for the parent backup job and transaction log backup job.
At each start of the SQL Server backup job ('parent'), a new .VLB is created to store log backups in the repository:
- If the Use per-VM backup files option is selected for the repository, then Veeam will create a separate .VLB for each server processed by the job.
- If this option is cleared, then a single .VLB will be created for all servers processed by the job.
For example, if a job processes only one SQL Server, the repository will contain a number of .VLB files for it (a so-called chain).
As described in the section above, during database log backup ('child') job session, transaction log backup is performed by native means of the SQL Server and stored as .BAK file to a temporary folder on the SQL Server VM guest file system. Then Veeam copies .BAK file to the current .VLB in the repository. When the new 'parent' job session starts, another .VLB is created, and the .BAK files that appear after that will be stored there during the 'child' job session. The resulting chain of .VLBs will look like shown below, depicted for a single SQL Server VM1:
Total number of all LOG<N>.BAK files stored at the moment in all VLBs is reported as a number of restore points for the 'child' job that backs up database logs. So, in the example above, the log backup job for SQL Server VM1 has created 8 restore points by the moment.
In the Veeam backup management console this number of restore points for the log backup job can be seen in the Restore Points column of the preview pane.