Separate Dump and Commit Frequencies
Configure the Runs every (dump) and Commit every (sweep) intervals independently. The Runs every value determines how frequently logs are transferred to backup media and defines the Recovery Point Objective (RPO). The Commit every value determines how frequently logs are written to backup storage and when backup jobs are created. Do not configure both intervals with the same value unless required.
For example, if log backups run every 1 hour:
- Setting Commit every = 4 hours reduces job count and Control Plane load while maintaining 1-hour RPO protection at the cache.
Use shorter dump intervals to meet RPO requirements. Use longer commit intervals to reduce job volume.
Align Dump Frequency with RPO
Set the Runs every value to match the required RPO. The dump interval defines the maximum potential data loss between log captures. Configure the interval based on business or compliance requirements.
For example,
-
15 minutes for strict RPO requirements
-
30–60 minutes for moderate RPO requirements
Avoid configuring dump intervals more frequently than required.
Optimize Commit Frequency
Set the Commit every value based on recovery requirements, storage considerations, replication needs, and job overhead. The commit interval determines when backup jobs are created and when logs are written to backup storage.
If backups from the primary copy must be synchronized to a remote site at a specific interval, configure the Commit every value to match the required synchronization frequency.
Examples:
-
If the remote site requires synchronization every 4 hours, set Commit every = 4 hours (minimum supported value). Increase the interval as needed, up to 24 hours, based on operational requirements.
-
If no frequent synchronization requirement exists, retain the default 8-hour commit interval. The default reduces job count and Control Plane processing while maintaining log protection at the configured dump interval.
This ensures logs are committed to the Control Plane and available for replication at the required frequency.
Adjust the commit interval as needed to balance recovery requirements, replication timing, and operational overhead.
Monitor SLA Compliance
Log backups are included in SLA calculations. Verify that SLA reports reflect the configured RPO. Configure alerts for missed log SLAs. Adjust the dump interval if SLA thresholds are not met.
Monitor Backup Media
Ensure sufficient storage capacity on the primary copy. In high-transaction environments, monitor storage utilization to prevent unexpected growth.