ability to extract data from VLB files, in order to allow the recovery of truncated logs #04738455

[makacmar]

Hello,

we have broken the log by creating a manual transaction log backup and the log was cleaned (truncated) by this
we have waited for the veeam child process to run a log backup.
In console we saw "Collected SQL Server transaction logs do not match any existing database backup"

After the veeam log backup run, the transaction log was also cleaned (truncated), the log backup file deleted as usual from the server.
if customer needs to recover database in sql, we need to extract log files to customer VM (same to extract archive logs in oracle)

[foggy]

Hi Marcel, if Veeam B&R has successfully completed the job with configured logs backup, it will be able to perform restores from the saved logs. Of course, it cannot perform point-in-time restores for the period it doesn't have valid logs backup for. If you feel the product behavior is not expected, please continue investigating with the help of our engineers. Thanks!

[makacmar]

Hello Foggy,
based on technician from case we were not able to restore logs only to customer VM.
we were not even able to extract logs from backup files.
Technician had to use internal extractor to do that and solution now is to open case with severity 1.

[foggy]

Not sure I fully understand the scenario. With Veeam B&R, you can perform database restores to any point in time available in the log files (not log files themselves though). In case logs were truncated and have not been successfully backed up or the chain was broken, there's nothing much Veeam B&R can do.

[makacmar]

we did scenario, that
incremental is done at 18:00
every 60 minutes is done child job with log
DB admin will create manual log 11:30
since this time child job is working, but is saying, that logs are not recognized to any DB, but they are backed up
customers DB broke at 14:00
we need restore - point in time available is till 11:30, but logs (11:30-14:00) are backed up and not available on VM
so restore into 14:00 requires restore of logs, which are not available
and technician closed session, that for restore of logs between 11:30-14:00 we need to open severity 1 to extract them by internal extractor as VBR does not offer currently any other solution

[foggy]

Understood, thanks for the step-by-step procedure. Our engineer is correct, Veeam B&R is not able to restore the log files in this case, this is beyond the scope at the moment.