What QCUL Protects Before a Laboratory Update

A laboratory restore point protects the copied environment’s update-relevant file and database state before installation so Undo Lab Update can credibly return the lab to its previous version.

Protected laboratory state

• Copied Joomla database tables/state needed to restore the pre-test lab.
• Files in the laboratory tree affected by the update/checkpoint scope.
• Version/evidence information used to verify the restored state.

What it does not protect

It is not a production backup and does not capture the live site for disaster recovery. It also cannot promise reversal of external third-party side effects an administrator manually triggers from the lab.

Why QCUL refreshes its runtime

After a restore, QCUL reapplies the current runtime so an older checkpoint cannot roll the signed installer/evidence endpoint backward and weaken the current laboratory control plane.

Preserve a known starting state

What QCUL Protects Before a Laboratory Update is useful only when the restore point and current laboratory belong to the same latest test operation. If you cannot prove that relationship, refresh the laboratory from current production and perform a new test rather than manually reconstructing a state and reusing old evidence.

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.