Account for full start windows when AWS Backup rules overlap

A longer-retention backup rule can suppress expected shorter-retention jobs across its entire start window.

Source facts

When AWS Backup rule start windows overlap, AWS Backup retains the backup under the longer-retention rule. Its optimization considers the full start window rather than only the nominal scheduled time. A job can remain CREATED while waiting to start and can become EXPIRED when its start window runs out. Snapshot scheduling and continuous point-in-time protection have different behavior.

Source: AWS — Backup plan options and configuration.

Applicability

This concerns backup-plan scheduling and overlap optimization. A chosen schedule does not establish a guaranteed backup completion time or an application recovery objective.

DSE recommendation

DSE recommends drawing the daily start windows for every effective rule on one timeline. Calculate the recovery-point pattern produced by overlapping windows before interpreting fewer jobs as a failure. Separate start deadlines from completion deadlines in monitoring. Ask the application owner to approve the resulting gap between usable recovery points, and review maintenance-window conflicts before reducing a start window to force a desired count. Give the recovery owner a simple timeline showing the resulting usable points, not only the configured rule names. Review that timeline whenever another rule is added so a well-intended retention change does not leave an unexplained monitoring expectation.

Verification

Proposed verification: observe a full approved test schedule and compare actual job start times, expiry states and retained recovery points with the planned timeline. Check the longest gap between usable backups. Keep failed-start alerts separate from intentionally optimized overlapping rules so operators can investigate the right condition.

Official reference

AWS — Backup plan options and configuration. Reviewed October 20, 2026.