Performance Issue VESQL - restore to specific transaction

[dbr]

Hi all,

I had an issue that loading data for fine-tune the restore point took felt forever (ok, it took about 10 minutes). For me that is too long therefore I filed a case. In the end we found out that the log backups didn't contain enough transactions and therefore all log backup were loaded regardless of selected point in time. Loading data for fine tune a restore point for a heavy utilized database is much faster because only one log backup is loaded to display fine tune data. Here my wish to R&D:

- Add a hint to documentation, that loading data (respectively loading transactionlogs) may take long time because more transaction logs are loaded due to too few number of transaction within one log backup file.
- Only load a small number of log backups regardless of the number of transactions in log backup for display fine tune data.
- A registry key to control log backup loading behavior for fine tune.

Could anyone please take this request into account?

Thanks,

Daniel

[dbr]

Addition:
- Add more information to fine tune dialog when loading data (mounting restore point, loading log backup x of y...)

[foggy]

Hi Daniel, thanks for your feedback, it is noted. By default, Veeam Explorer for SQL loads the number of transaction logs required to get 200 transactions back and 200 forward from the specified point in time. This can be changed using the FineTuningMaxLoadedItems parameter in its configuration file (C:\ProgramData\Veeam\Backup\SQLExplorer\config.xml).