Hi all,
I’m looking into the default configuration for SQL transaction log backups in Commvault and noticed that log backup with caching (Log Commit) is enabled by default.
From what I understand, the log backups are first cached on the MediaAgent and then committed in batches to the CommServe based on a defined interval. I also see that even if log backups run frequently, they don’t appear as individual recovery points in the timeline, but are still used for point-in-time restores.
What I’m trying to understand is how useful this setup is in practice. Since log backups are not visible as recovery points in the timeline, does this approach actually help you in real scenarios?
Is anyone actively using this default behavior and finding it beneficial, even though you don’t see those recovery points directly?
Would be interested to hear your experience.
Best regards,
Nikos
