Use QCBM Receiver with Scheduled Backups on Low-Traffic Joomla Sites

QCBM Receiver can do more than collect finished Recovery Packages. Authenticated Receiver polling can also start or advance QCBM's own due scheduled-backup work, which is useful on Joomla sites that receive too little browser traffic to wake background work reliably.

This assistance is deliberately limited to QC Backup Manager. Receiver is not a generic remote Joomla scheduler and cannot be used to run arbitrary Joomla Scheduled Tasks.

Configure Scheduling in QCBM First

Create and publish the Backup Profile you want to run automatically, configure its schedule, and keep the QCBM scheduled-backup runner enabled in Settings. Scheduled backups must also be allowed by the current entitlement; Receiver itself requires Max or All Access.

The Profile schedule remains the authority for when a backup becomes due. Receiver does not invent a separate Windows backup schedule.

Keep an Active Receiver Connection Running

Pair the Joomla site with QCBM Receiver and leave the Windows background service running. Each authenticated poll gives QCBM an opportunity to evaluate its own scheduled profiles.

The site must remain reachable over HTTPS, and the paired device credential must still be active.

How Receiver Assists a Due Backup

If QCBM finds a due Profile and there is no conflicting persistent backup, the Receiver request can start QCBM's normal persistent scheduled-backup routine directly with a Receiver run source. QCBM then advances that saved Backup Set through bounded workers.

While a Receiver-assisted scheduled Backup Set is queued or running, subsequent polls can continue the same job. QCBM uses a short assist interval while that work is active so a quiet site can make progress without waiting for unrelated frontend traffic.

No Separate Cron Is Required Solely for Receiver-Assisted QCBM Backups

The current QCBM Receiver design deliberately bypasses Joomla's generic lazy-scheduler dependency for this narrow workflow. When Receiver is running, QCBM's own due scheduled backups can start and continue from authenticated Receiver polls without setting up a separate cron just to wake QCBM.

This does not disable Joomla's scheduler or turn Receiver into a replacement for it across the site. Other Joomla tasks continue to use their own configured execution method.

Receiver Does Not Take Over Manual Backups

If an unrelated/manual persistent Backup Set is active, Receiver does not take ownership of it. QCBM reports that backup as running and Receiver waits. This protects the single persistent backup workflow from duplicate or competing operations.

After Completion, Receiver Can Collect the Package

When the scheduled Backup Set finishes and its canonical Recovery Package is verified, the same Receiver can immediately receive it if that paired device has not already recorded a verified receipt.

Receiver independently checks the downloaded size and SHA-256 before acknowledging custody. The optional delete-after setting is evaluated only at that verified acknowledgement stage.

Verify Low-Traffic Operation

  1. Use a Profile with a near-term schedule for a controlled test.
  2. Keep the Receiver service running while avoiding manual Joomla traffic intended to wake the scheduler.
  3. After the Profile becomes due, review QCBM Backup History and confirm a scheduled Backup Set starts and reaches verified completion.
  4. Confirm Receiver downloads and verifies the resulting Recovery Package.

If nothing starts, check that the Profile is published and actually due, scheduled backups are enabled in QCBM Settings, the entitlement is valid, the Receiver device is active, and HTTPS polling is reaching the site.

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.