Disk Caching for Frequent Database Log Backups

Applies to: Microsoft SQL Server on Linux, Microsoft SQL Server on Windows, Oracle, Oracle RAC, SAP HANA

You can optimize database log backup recovery point objectives (RPOs) and have log backups running independently of the Control Plane maintenance windows. You can run database log backups at a greater frequency, in a scalable manner. Disk caching of log backups uses compression to save space and encryption for greater security.

Without disk caching for log backups, if you run transaction log jobs frequently, then you must manage those scheduled jobs. However, with disk caching for log backups, log files are backed up at the desired frequency using native backup utilities, are cached to a mount point on the MediaAgent, and are available for database restores. The Scheduler runs only at the interval defined in the backup plan when you turn on the Use disk cache for log backups toggle and configure the Commit every setting to ensure cached data is committed.

If you turn on the Use disk cache for log backups toggle, backup windows, which define when backup operations run, do not apply to database log backups using disk caching. This is because one goal of disk caching is to run disk caching backups as defined in the schedule, regardless of a maintenance window or downtime.

Disk caching of log backups is also supported using a HyperScale X configuration. The following lists the CVFS versions necessary on HyperScale X to support disk caching:

  • For SQL Unicode database support, the CVFS version must be 4.7.6 or greater.

  • For other databases, the CVFS version must be 4.7.4 or greater.

You can cache database logs on a disk library or on a cloud library. You can use one of the following cloud libraries for disk caching: Amazon S3, Google Cloud Storage, or Microsoft Azure Storage.

Loading...