# 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.

- Canonical URL: https://update.dsesecurity.com/updates/aws-backup-overlapping-start-windows-retention-optimization/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-10-20T18:14:03+00:00
- Modified: 2026-10-20T18:34:30+00:00
- Last reviewed by DSE: 2026-10-20
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, Cybersecurity, IT
- Reading time: 2 minutes

## What you need to know

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

## Potentially affected

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.

## Article

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](https://docs.aws.amazon.com/aws-backup/latest/devguide/plan-options-and-configuration.html).

## 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](https://docs.aws.amazon.com/aws-backup/latest/devguide/plan-options-and-configuration.html). Reviewed October 20, 2026.

## Primary reference

- Name: AWS — Backup plan options and configuration
- Authority: docs.aws.amazon.com
- URL: https://docs.aws.amazon.com/aws-backup/latest/devguide/plan-options-and-configuration.html
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Account for full start windows when AWS Backup rules overlap,” DSE Security, https://update.dsesecurity.com/updates/aws-backup-overlapping-start-windows-retention-optimization/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.