Lab Restore Points versus Production Rollback Checkpoints
Lab restore points and production rollback checkpoints both support undo, but they protect different environments, are created at different times, and have different lifecycles.
Compare them
| Characteristic | Lab restore point | Production rollback checkpoint |
|---|---|---|
| Target | Private laboratory only | Live production update scope |
| Created | Automatically before a protected lab test | Only when administrator selects temporary QCUL protection before push |
| Undo action | Undo Lab Update | Undo Production Push |
| Availability | Latest valid lab test while lab exists | Successful push while checkpoint/window remains valid and not superseded |
| Scope | Lab files/database state | Observed update-related production scope; Joomla core protection is broader |
| Lifetime | Ends with refresh/remove or loss of valid latest point | Expires after configured 10–240 minute window or lab removal |
| Backup replacement? | No | No |
Use both for different purposes
Lab undo proves you can return the private test to its start and retest. Production checkpoint undo provides a short live-site operation rollback after a controlled push. Keep an independent full backup regardless.
Preserve a known starting state
Lab Restore Points versus Production Rollback Checkpoints 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.