Applies to: DB2, DB2 MultiNode, Informix, Microsoft SQL Server on Linux, Microsoft SQL Server on Windows, MySQL, PostgreSQL, Oracle, Oracle RAC, SAP HANA.
Serverless Log Backups provide high-frequency transaction log protection without requiring Commserve connectivity. Transaction logs are first written to backup storage and then committed based on configured schedule settings. Log dump operations continue even if the Commvault Control Plane/CommServe computer is temporarily unavailable. Backup metadata is synchronized when connectivity is restored. This feature supports short Recovery Point Objectives (RPOs) and reduces dependency on continuous Control Plane availability.
When to Use Serverless Log Backups
Serverless Log Backups are useful in environments where:
-
Short Recovery Point Objective (RPO) intervals are required.
-
Transaction log growth must be controlled through frequent log truncation.
-
Control Plane availability may be intermittent.
-
Control Plane resource utilization must be minimized.
-
Regulatory requirements mandate frequent log backups.
By separating the log dump frequency from the log commit frequency, the feature provides fine-grained RPO control without increasing Control Plane load or creating unnecessary backup jobs.
Serverless Log Backup Process Flow
-
Transaction logs are generated by the database.
-
Logs are dumped to a backup storage based on the Runs every setting.
-
Log backups are finalized and registered as a CommServer job according to the Commit every configuration.
-
Backup metadata is updated on the Control Plane/CommServe computer.
Additional Information
Log data is transferred using the Secure Data Transfer (SDT) pipeline, which encrypts and compresses data in transit.
Log dump operations continue independently of Control Plane availability. Commit operations create backup jobs and update metadata.