Why a QCUL Production Checkpoint Is Not a General Backup

A QCUL production checkpoint is optimized to reverse one tested update operation and is deliberately not a substitute for full-site backup, disaster recovery, or historical retention.

Scope limitations

• Protects update-related production database/file scope, not every unrelated file/system.
• Joomla core checkpoints protect all Joomla-prefixed tables, but external databases/services remain outside the checkpoint.
• Expires after the configured short rollback window.
• Is removed with the laboratory/cleanup lifecycle.
• Does not provide long-term backup browsing/version history.

What a full backup adds

A verified external backup can recover from unrelated corruption, administrator mistakes, infrastructure failure, security incidents, or problems discovered after the QCUL rollback window. Maintain that broader recovery layer before production changes.

Recovery discipline

When working with Why a QCUL Production Checkpoint Is Not a General Backup, keep the independent backup available even if the QCUL checkpoint is valid. The checkpoint is a fast, short-lived update rollback mechanism; if its protected scope, validity window, or verification cannot satisfy the incident, move to the broader recovery plan rather than extending QCUL beyond its promise.

Community Discussion

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