# Serverless Log Backup Configuration Notes

Applies to: DB2, DB2 MultiNode, Informix, Microsoft SQL Server on Linux, Microsoft SQL Server on Windows, MySQL, Oracle, Oracle RAC, SAP HANA, PostgreSQL

- You can optimize database log backup recovery point objectives (RPOs) and have log backups running independently of the Control Plane or CommServe computer maintenance windows. You can run database log backups at a greater frequency, in a scalable manner, without adding to the workload of the CommServe computer.

- Serverless log backups uses compression to reduce storage requirements and encryption to enhance security.

- Log backups continue to run even when the CommServe computer is down for maintenance or when connectivity to the CommServe computer is disrupted. With serverless log backup enabled, you can set the log RPO as low as 5 minutes.

- With serverless log backups, you can run frequent transaction log backups without managing schedules or storing job data on the CommServe computer. Instead, native backup utilities back up log files at the specified frequency, cache them to a mount point on the MediaAgent, and make them available for database restores. The scheduler runs only at the interval defined by the Use serverless log backups and commit every setting to ensure that cached data is committed to the CommServe computer.

- When Serverless log backups is enabled, any interactively submitted job that performs a log backup uses serverless log backup. The job history for these jobs shows an application size of 0 to avoid double counting when capacity licensing is enabled.

- If you enable the Use serverless log backups and commit every setting, backup windows do not apply to database log backups that use serverless log backup. Backup windows define when backup operations run. The serverless log backup runs backups according to the defined schedule, regardless of CommServe maintenance or downtime.

- If you already run scheduled log backups and want to use Serverless log backup instead, select Use serverless log backups and commit every checkbox. Then, specify the interval between log commit operations to the CommServe computer.

- At intervals defined by the Use serverless log backups and commit every setting, a scheduled job commits all cached log backups since the previous job to the CommServe computer. The application command-line log backups do not create jobs in the Job Controller when writing logs to the serverless log backup. Only commit jobs create entries and appear in the backup history.

### Oracle, SQL and SAP HANA Database

- For Oracle and SQL, the parameters defined for the database type control how often the system checks whether a log backup should run. If the maximum time defined by the Force a backup every setting elapses without a backup, the system runs a log backup.

- When SAP HANA initiates a log backup through the Commvault Backint interface, the system caches logs to a mount point on the MediaAgent.

- At intervals defined by the Use serverless log backups and commit every setting, a scheduled job commits all cached log backups since the previous scheduled job to the CommServe computer.

### DB2, DB2 MultiNode, MySQL, Informix and PostgreSQL Database

- For DB2, DB2 MultiNode and MySQL, when a log archive operation is initiated through the native backup utility, the system caches logs to a mount point on the MediaAgent.

- For PostgreSQL, Each archived transaction log is copied to the MediaAgent. This behavior is configured by modifying the archive_command in postgresql.auto.conf to copy logs to the backup storage location and then reloading the configuration file.

- When log caching is enabled for DB2 archive logs, the system triggers log archival based on the schedule defined by the Use serverless log backups and commit every setting in the plan.

- For Informix, when a log backup operation is initiated with ON-Bar, the transaction logs and ixbar file are copied to the MediaAgent.

Note

- Caching is not supported on tape libraries. You can cache database logs on a disk library or cloud library. Supported cloud libraries for serverless log backup include: Amazon S3, Google Cloud Storage, or Microsoft Azure Storage.

- To use serverless log backup, the MediaAgent computer and the client computer must be different. Do not enable serverless log backup for an agent on the same MediaAgent that hosts the disk library.

- To enable Serverless log backup, all database server clients must use Indexing V2. This requirement does not apply to SQL Server clients.

- For MySQL, the Serverless log backup is supported only for MySQL traditional backups. To enable this setting, you must enable the $EnableDumpSweepFeatureForMySQL additional setting. The Serverless log backup is not supported for MySQL Cluster and Proxy Backups configurations.

- For PostgreSQL agent, enabling the serverless log backup feature updates the archive_command to copy logs to the MediaAgent. To append to the existing archive_command instead of overwriting it, set the bPreserveArchiveCommandWithDumpSweep (PostgreSQL) to 1.

- The Serverless log backup is not supported for the Media Parameter and Oracle Data Guard features.

- The Live Sync replication is not supported for PostgreSQL instance with serverless log backup enabled.

×

Loading...