How to Choose Between the Two Production-protection Options
QCUL offers two production-protection choices because some administrators already have a verified recovery system while others want a fast update-scoped QCUL undo path.
Compare the options
| Option | Best when | QCUL Undo Production Push |
|---|---|---|
| Existing verified recovery method | You already have a current full-site backup/recovery workflow you trust and can restore independently. | No. Recovery is performed through your external method. |
| Temporary QCUL rollback checkpoint | You want QCUL to capture the selected update’s protected live scope immediately before push. | Yes, while the checkpoint/window remains valid and no newer operation supersedes it. |
Use both layers responsibly
Even when choosing the temporary QCUL checkpoint, keep the independent backup. The QCUL checkpoint is optimized for reverting one update operation; it is not a full disaster-recovery archive.
Choose before push
The protection method is part of readiness. You cannot create a trustworthy pre-update QCUL checkpoint after a push has already changed production.
Production change rule
For How to Choose Between the Two Production-protection Options, the live site should change only through the explicit tested-item production workflow after current readiness checks pass. Do not substitute a new package, skip the review/protection decision, or run a second production action while QCUL already owns an active push/rollback state.
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.