qTest Manager Recovery Decision After a Failed On‑Premises Upgrade

When a qTest Manager on‑premises upgrade fails, teams must decide whether to revert to the pre‑upgrade version by restoring the full backup or to proceed with a fix‑forward to the intended target version. The choice hinges on identifying whether the failure occurred before or after the irreversible schema migration step, a detail that is not always exposed by the installer logs and varies across version paths. Tricentis documentation emphasizes backups as the primary safety net, yet it does not give a clear rule for when a forward repair is viable.

Determining the safest recovery path requires evaluating the failure point, the availability of a tested restore procedure, and any version‑specific constraints that could make a fix‑forward attempt risky or unsupported.

• What indicators reliably show whether the upgrade failed before or after the database schema migration?
• Under what conditions is a fix‑forward to the target version considered safe according to Tricentis guidance?
• How should administrators weigh the risks of a partial rollback versus a forward repair when external integrations are involved?