In other words, you specify the desired point in time to recover to, DB server VM gets reverted to the closest restore point available before a corruption occured, after that transaction logs are applied. Does this answer your question?Database will be recovered to the closest VM restore point before the moment you specify on the timeline, and then transaction log replay will bring the database to the necessary state.
I'm not sure if I follow you...incremental and synthetic are mutually exclusive things in Veeam terminology. Could please clarify that a little bit? What did you choose in job options?daily incremental synthetic backup
To make an transactionally-consistent backup Veeam leverages sql internal mechanisms. It means that if your engine allows processing of transaction logs when in corrupted state then you'll need to choose point in time manually. If your database engine does not allow log processing on a corrupted instance, then point in time recovery scale will contain only non-corrupted RPs.How is Veeam aware that corruption to the to the DB occurred?
Correct. First Veeam restore your VM to the most recent RP and then applies transaction logs in order to get DB as close as possiblle to the last known healthy state.if we do a full backup and CHECKDB every night, and discover on Thursday morning that CHECKDB showed corruption, I could select the most recent restore point (Wednesday night), open the Veeam Explorer for SQL Server and Veeam would ignore the Wednesday night full database backup and use the Tuesday night full database and roll forwards?
Users browsing this forum: Google [Bot], spfoster72 and 30 guests