SQL Log Backup – Log Commit default behavior

Hi ​@Nikos.Kyrm,

I must admit I have disabled all these log caching rules on our main MSP platform. But based on documentation, this feature will allow you to reduce load on the Commserve (less jobs = less load) while still having backups run during CommServe outage or outside backup windows.

Configurations for RPO

For point-in-time restores, the restore points do not matter as Commvault allows you to pick the exact time to restore to using the custom time field under the restore points bar. During restore, Commvault will replay all transactions up to the restore time to allow the database to be restored to a specific time that is not restricted by restore points.

Restoring a SQL Database In-Place

I think the choice to make this option default is a sensible one to ensure database logs are as protected as possible.

Hope this explanation makes the reason why this is enabled more clear.

Kind regards,

Paul

Hello ​@Paul G,

Thanks for your reply! Yes, I agree that in the documentation "Log Commit" is recommended, but still, how many backup admins are actually keep this option enabled?

Best regards,
Nikos

Dump

I assume that majority still uses the old, more controllable setup. 

Bumping this question up, as still some clarification is required.

Based on Paul’s screenshot, it doesn’t seem possible to select the individual recovery points that should exist according to the log commit configuration. Currently, users can only select committed jobs from the timeline or job history, even though there should be additional recovery points available.

This makes the solution seem less granular than a standard t-log backup job, additionally database monitoring tools are not seeing these commits as actual t-log backups, so additional alerts are being triggered. 

With the configuration below, I would expect the following behavior:

• A t-log backup task is triggered every hour and the data is saved to backup storage directly by the commit task.
• Based on the automatic disk utilization rules, the commit task periodically processes the accumulated data as a backup job.
• Users should still be able to see and select all individual t-log recovery points from the timeline, not only the committed backup jobs.

Configuration screenshot for the reference