Understand QCBM Readiness Cards

QCBM Readiness Cards turn several important backup dependencies into focused checks. They are not a single pass/fail score: each card answers a different question about whether this Joomla installation is ready to create, keep, export, or recover a dependable Backup Set.

Read the card that owns the problem you are investigating instead of changing unrelated settings.

Recovery Readiness

Recovery Readiness answers the most basic recovery question: does QCBM currently have at least one verified Backup Set? A verified set is sealed into a ready-to-use Recovery Package ZIP containing the standalone runner, instructions, manifest, and required backup parts.

If the card says no verified Backup Set exists, creating more Profiles does not solve that condition. Complete and verify a real backup first.

Storage Health

Storage Health reports the configured Managed Private Storage path, QCBM's storage-location assessment, and the last direct-URL access test. Storage outside the webroot is preferred; compatibility storage inside the webroot requires the protection test to confirm it cannot be fetched directly.

Use Run Direct URL Test when the card calls for it. A writable folder is not automatically safe if the web server can expose backup data.

Scheduler Health

Scheduler Health reports whether QCBM's Joomla Scheduled Task routine is present and shows the saved Last run and Last result for scheduled backups.

This is separate from the Entitlement Automation Integrity card. A site can have healthy entitlement revalidation while scheduled backup execution still needs attention, or the reverse.

Update Delivery

Update Delivery checks the Joomla update-site wiring that belongs to the QCBM package. A healthy configuration has one matching enabled update site associated with the QCBM package rather than the component alone, with the current update identity ready.

The card verifies configuration, not whether a particular new release exists. After fixing update-site wiring, still run a real Check for Updates.

Large Site Readiness

Large Site Readiness uses a safe sample of the site to recommend archive behavior and a split target. It reports the sampled size and can warn when the readiness scan stopped early.

Treat the sample as planning evidence, not an exact prediction of final working-space requirements. Large backups use bounded/resumable work, and temporary working space can exceed the final Recovery Package size.

Export Health

Export Health summarizes the state of configured off-site destinations. Use it to distinguish a general destination/configuration problem from a particular Backup Set export failure.

When the summary needs attention, open Settings and test the affected destination with the provider-specific test before retrying a large export.

Data Integrity

Data Integrity checks QCBM database relationships and aggregate consistency. It also records when the last full file/checksum check was performed.

Administrators with the integrity permission can use Run Full Check. Repair Safe Metadata is for repairable metadata relationships; it is not a general command to rewrite backup files or ignore a failed checksum.

Use the Cards Before a Critical Change

Before a Joomla core update, major extension upgrade, PHP change, hosting move, or other risky maintenance, look for a verified Backup Set and review Storage Health, Scheduler Health, Update Delivery, and any destination warnings relevant to your workflow.

A green card is useful evidence, but disaster-recovery confidence ultimately comes from having a verified Recovery Package and periodically testing recovery.

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.