How Laboratory Restore Points Work

Before each protected laboratory test, QCUL creates a restore point for the current lab state so the latest tested update can be undone without touching production.

Restore-point purpose

The restore point captures the private laboratory database/file state before the selected update. It is run/operation-specific and belongs to the lab test, not to production recovery.

Lifecycle

1. QCUL confirms the selected update is testable.
2. It checkpoints laboratory database and files in restartable batches.
3. Only after checkpoint completion does the package install in the laboratory.
4. If Undo Lab Update is chosen later, QCUL restores the checkpoint, reapplies the current QCUL runtime, verifies the original version, and reruns basic checks.

Only the latest operation is undoable

QCUL does not remove an older update from beneath later cumulative lab changes. If you need an earlier clean production state, refresh the laboratory rather than trying to reverse history out of order.

Preserve a known starting state

How Laboratory Restore Points Work 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.