Configure Retry Timing for Failed Scheduled Backups

A QCBM Profile can define how long the scheduler waits before the same scheduled occurrence is eligible to try again after an unsuccessful attempt. This prevents a failing backup from being launched repeatedly on every scheduler poll.

The retry wait is part of the Profile's exact schedule settings and is available with scheduled backups on Pro, Max, and All Access.

Set the Retry Wait

  1. Go to Components > QC Backup Manager > Profiles.
  2. Edit the scheduled Profile.
  3. Open the Backup and Exact Schedule section.
  4. Find Retry wait after a failed attempt.
  5. Choose 15 minutes, 30 minutes, 1 hour, 2 hours, 6 hours, 12 hours, or 24 hours.
  6. Save the Profile.

QCBM stores the retry wait with that Profile. Changing it affects future scheduler decisions for that Profile; it does not change other Profiles.

What the Retry Wait Actually Controls

For hourly, daily, weekly, and monthly schedules, QCBM identifies the scheduled occurrence that should have run. If an attempt for that occurrence is recorded as failed, running, or pending, QCBM suppresses another attempt until the configured retry interval has passed.

When the interval expires, the same occurrence can become eligible again if it has not already completed successfully. A successful, verified scheduled occurrence is not retried simply because the scheduler checks again.

Retry Timing Does Not Move the Normal Schedule

Suppose a daily Profile is due at 02:00 and fails at 02:03 with a 30-minute retry wait. QCBM can make that 02:00 occurrence eligible again after the wait rather than redefining the Profile as a 02:33 schedule. The next normal daily occurrence still comes from the Profile's calendar rule.

The Profiles/scheduler display can report Retry after followed by the calculated local time while the wait is still active.

Persistent Jobs Are Continued, Not Duplicated

The retry setting is not permission to start another Backup Set while the first persistent job is still active. QCBM checks for an unfinished scheduled job and advances that saved Backup Set through bounded worker checkpoints instead of starting a duplicate.

If another manual persistent Backup Set currently owns the backup-create operation, scheduled creation is deferred cleanly. That situation is different from a completed failed attempt that is waiting for its retry interval.

Special Behavior for Every Scheduler Check

The advanced Every scheduler check rule also observes a cooldown based on the Profile's retry setting. QCBM enforces at least a 15-minute interval between attempts even if Joomla polls the task more frequently.

If you do not actually need very frequent backups, prefer an hourly, daily, weekly, or monthly rule. Calendar schedules are easier to understand when reviewing Backup History.

Choosing a Practical Retry Wait

Use a shorter wait when failures are likely to be temporary and the site has enough resources to try again soon. Use a longer wait when an unsuccessful run is likely to require administrator attention, substantial disk space, or recovery from hosting/provider limits.

A retry wait cannot fix a persistent configuration problem. Insufficient storage, unavailable archive support, invalid Recovery PIN configuration, unreadable files, or an unhealthy destination should be corrected rather than retried indefinitely.

Verify Retry Behavior

After saving the Profile, review its next-run label. If a scheduled attempt fails, check Backup History for the actual failure phase/message and then confirm the Profile reports the expected retry time. When the wait expires, the next healthy task poll can re-evaluate that occurrence.

Do not create a second manual backup merely because a scheduled job looks slow. First confirm whether QCBM already has an active or resumable persistent job.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.