Hi @SanjivK -
You should follow the Veeam Explorers Guide on how to restore SQL to a point in time. The Guide provides steps on how to do so:
https://helpcenter.veeam.com/docs/backup/explorers/vesql_restoring_pit.html?ver=120
That should get you going.
Best.
You should use Veeam Explorer for Microsoft SQL Server. It can automatically replay the logs and let you restore the database to an exact point in time without needing to run manual steps in SQL Server.
If transaction log backups were not configured in Veeam, then you’ll only be able to restore to the latest full or differential backup. In that case, log replay must be done manually in SQL Server by restoring the database with NORECOVERY.
adding more about the query-
SQLAG Point-in-Time Restore with NORECOVERY – Applying Transaction Logs Post-Restore
- I’m restoring a database to a specific point in time using Veeam.
- I’m using the NORECOVERY option during the restore to keep the database in a restoring state.
- During the restore process, new transaction logs are generated on the SQL Server.
- After the restore completes, I want to apply those transaction logs to bring the database fully up to date.
Follow the link that Shane posted as that will walk you through the steps.
Veeam can handle transaction log replay up to the restore point you select, but it won’t apply transaction logs that were generated on the SQL Server after the backup job. If you want to include those, you’re on the right track using NORECOVERY during the restore, because it keeps the database in a restoring state.
Once Veeam finishes the restore, you can manually apply the subsequent transaction logs using SQL Server Management Studio with the standard restore log for each log in sequence.
Since you are already able to select a point-in-time restore in Veeam, the best method is to use the default restore mode, as Veeam itself will automatically apply the necessary logs to reach the timestamp you choose — no manual steps needed.
@SanjivK - you can only restore via Veeam from files (backups & transaction logs in this case) Veeam has already backed up. Veeam cannot be used for files taken after the backup (& before the next backup). In that case, you would need to then transition to use SQL restore methods.
Best.
Veeam can handle transaction log replay up to the restore point you select, but it won’t apply transaction logs that were generated on the SQL Server after the backup job. If you want to include those, you’re on the right track using NORECOVERY during the restore, because it keeps the database in a restoring state.
Once Veeam finishes the restore, you can manually apply the subsequent transaction logs using SQL Server Management Studio with the standard restore log for each log in sequence.
Since you are already able to select a point-in-time restore in Veeam, the best method is to use the default restore mode, as Veeam itself will automatically apply the necessary logs to reach the timestamp you choose — no manual steps needed.
@matheusgiovanini Do you have any step-by-step article for - “Once Veeam finishes the restore, you can manually apply the subsequent transaction logs using SQL Server Management Studio with the standard restore log for each log in sequence.”
