Broken log sequence chain detection

[Antoine F]

With regards to SQL backups, does Veeam have a mechanism to handle broken log sequence when performing backups.

e.g. option to perform a full when broken chain happens or detection and alerting or some other mechanism.

[Gostev]

We use native SQL Server capability to perform transaction log backups, so in the above scenario the log backup will fail with the corresponding error message logged because SQL Server itself will spot the inconsistency (and we will pass on the error message into the job session log). Thanks!

[Antoine F]

Thanks Gostev,

If we talk about the native SQL backup, usually LSN errors occur during the "restore".
The backup does not generate LSN error exept maybe if there was no initial full backup which might be a different error.

However, some backup solutions keep track of the LSN when performing the backup and therefore detect if a LSN is missing due to a conflicting backup solution.

I am trying to figure if Veeam has means to detect issues before the need for the restore arise either through regular restore tests.

If not, I would like to know if there are planned alternatives like restoring the full backup and transaction log backup files from both conflicting systems and applying them manually.

Thanks again