Choosing an Existing Recovery Method for Production Protection

The existing-recovery option tells QCUL you will rely on a separate verified full-site recovery method rather than a temporary QCUL production checkpoint.

Step-by-step procedure

  1. Confirm you have a current, independently verified full-site recovery method outside QCUL.
  2. In the tested update’s production protection controls, choose the existing/verified recovery option.
  3. Do not claim recovery is verified unless you know where it is stored and how to restore it.
  4. Continue to Push to Production only after QCUL readiness checks pass.
  5. Understand that this option does not create QCUL Undo Production Push; recovery remains your external process.

What you give up

Because QCUL does not create a production checkpoint under this option, Undo Production Push is not available from QCUL for that push. If production needs to be restored, you must use the external method you selected and verified.

When this option makes sense

Use it when you already have a strong recovery product/process and do not need QCUL’s short-lived operation-scoped rollback. The existence of “a backup somewhere” is not enough; know that it is current, restorable, and accessible during the maintenance window.

Production change rule

For Choosing an Existing Recovery Method for Production Protection, 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.