TL;DR
- Log backup with caching will become the default behavior in Commvault 11.38.26, introducing a two-stage backup process that writes transaction logs to a temporary cache before committing them to final storage.
- The new architecture uses background dump processes and scheduled sweep jobs to reduce job manager congestion and prevent backup gaps when the Command Center control plane is unavailable.
- Configuration is straightforward through Command Center backup plans, where administrators can enable disk caching and set sweep job frequency in hourly increments starting at one hour minimum.
This tutorial demonstrates how to configure and use log backup with caching in Commvault Command Center, a feature designed to improve the reliability and performance of transaction log backups for databases including SQL Server, Oracle, SAP HANA, and DB2. The video explains how traditional transaction log backups can create job manager congestion and leave databases vulnerable to backup gaps when the Command Center control plane experiences downtime. Log backup with caching addresses these challenges by introducing a two-stage process: dump processes that run in the background and write transaction logs to a temporary cache, followed by sweep jobs that commit cached logs to final storage on a scheduled basis. This architecture ensures continuous database protection even during control plane outages, prevents job backlogs, and reduces visibility clutter in the job manager. The presenter walks through the configuration process in Command Center, showing how to enable caching within backup plans and adjust sweep job frequency. The video also covers monitoring and alerting capabilities through SLA reports, ensuring administrators maintain visibility into backup health despite the background nature of dump processes. With this feature becoming the default behavior in Commvault version 11.38.26, the tutorial provides essential guidance for database and backup administrators preparing for this architectural shift in transaction log protection.
Chapters
0:00 - Introduction to Log Backup with Caching 1:01 - Traditional Transaction Log Backup Process 1:35 - How Caching Changes the Workflow 2:56 - Enabling Caching in Command Center 4:27 - Monitoring and SLA Reporting
Key Quotes
0:07 - this feature already does exist and helps to manage transaction log backups, but because it is so useful, as I mentioned, it's going to become the default0:41 - if the control plane has any issues and the comm serve goes down, well, unfortunately, those jobs start running and that can create a very large backlog2:38 - The biggest benefit of this is that, if there is a failure with command center, then your jobs will still continue to run on the backend. There's no downtime and there's no getting a large backlog of transaction logs to chew through when everything is back up.
