This reply relates to Case id #01819616
Experienced the described situation.
Thus I must insist on a Feature Request for the limitaion
Veeam does not allow the restore of logs from multiple backup job executions
Full backups every 12 hours at 06:00 and 18:00.
Log backup every hour.
The situation was:
Thursday morning SQL Server started to log logical consistency-based I/O error (error 824) in the errorlog.
Friday afternoon the errors was discovered.
The application server was stopped Friday short before 18:00 and we waited for the next log backup to finish.
The errors was in a single data/ndf file and not in the transaction log, so normally (as when we used native backup tools) we would have restored a full backup from Wednesday 18:00 and applied all subsequent logs. By doing this we would have been able to restore the database without data loss at all.
Due to the limitaion this was not possible.
We did a test restore covering Thursday morning to prove restore was possible without data loss. The test restore was based on the full backup from Wednesday 18:00 with logs applied until Thursday 18:00 (This was possible due to a missing restore point Thursday 06:00 !?). DBCC CHECKDB showed no errors in the restored database.
PS/End of history: After a "DBCC CHECKDB ... REPAIR_ALLOW_DATA_LOSS" the databasen showed a corrupt index and corruption in another table. The index was rebuild but a lot of data was lost in the table. Fortunately the table was a table containing (non important) logging/history information. So it was decided to continue production with the loss of data in the logging/history table.