Schedules Run Unexpectedly in Legacy Retention Mode

Product versions: 11.2

Last modified: 22 April 2026

Problem

Backup jobs configured with multiple schedules in the legacy retention approach may run using an unexpected schedule:

  • A periodical schedule runs instead of a monthly or yearly schedule

  • The selected schedule does not match the expected priority

  • Job execution appears inconsistent when schedules overlap

Background

In the legacy retention approach, multiple schedules can be configured for a single job.

  • The product does not apply schedule prioritization rules in legacy mode.

  • When schedules overlap or share the same start time, one schedule is selected non-deterministically.

  • The selected schedule may vary between runs and cannot be predicted

This behavior is expected in legacy mode and is not considered a defect. In contrast, the improved retention (schedule retention) approach:

  • Applies strict schedule prioritization

  • Ensures predictable execution

  • Skips lower-priority schedules when conflicts occur

Solution

To ensure predictable schedule execution:

  • Switch to the improved retention (schedule retention) approach.

  • If the legacy retention approach must be used:

    • Avoid configuring multiple schedules with overlapping start times.

    • Stagger schedule start times (e.g., 02:00, 02:10, 02:20)

    • Minimize the number of schedules per job