If the current log backup schedule is hourly or several times a day, you can use disk caching of log backups to decrease the load on the CommServe computer. You can run log backups at a greater frequency, in a scalable manner, without adding to the workload of the CommServe computer. Log backups continue to work even if the CommServe computer is down for maintenance or if connectivity to the CommServe computer is disrupted. With disk caching enabled (Use disk cache for log backups option) the log recovery point objective (RPO) can be set to as low as 5 minutes.
Any interactively submitted job that results in a log backup uses disk caching when the feature is enabled.
Backup windows, which define when backup operations are to be run, are not applicable 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 CommServe computer's maintenance or downtime.
Disk caching of database log backups is available using Oracle third-party command line scripts. To meet your backup requirements, schedule the scripts using Unix crontab jobs.
Note
Disk caching of log backups is not supported in HyperScale X environments.