Prepare for a Joomla Site Recovery with QC Backup Manager

Successful recovery starts before you extract the package. Gather the correct verified Recovery Package, its four-digit PIN, the destination information, and any database or hosting credentials you will need before making changes to the target.

QCBM's Recovery Runner includes protected rollback features, but you should still preserve valuable destination data independently before a destructive recovery.

1. Choose the Correct Recovery Package

Use the newest verified Backup Set that represents the state you intend to restore. Confirm that you have the complete Recovery Package ZIP and the Recovery PIN assigned when that Backup Set was created.

If the package was copied between systems, keep the original off-server copy until the recovery is finished.

2. Preserve the Destination

If the destination contains files or database data that may matter, make an independent backup or snapshot before recovery. QCBM can create protected rollback state for supported destructive operations, but that protection belongs to the recovery process and should not be your only preservation layer.

3. Confirm the Destination Joomla Root

The Recovery Runner always treats the physical directory containing qcbm-recover.php as the locked Joomla root. You cannot type another target root into the browser.

Therefore, extract the Recovery Package into the exact directory you intend to recover. If you need to recover another folder, place the package in that folder instead.

4. Prepare HTTPS Access

Use HTTPS whenever the destination can provide it. The recovery session can include the Recovery PIN and database credentials, so encrypted transport is strongly preferred.

If TLS is not available yet on a new destination, the runner can continue over HTTP with a warning. Treat that as a temporary recovery condition rather than the preferred operating state.

5. Prepare the Database

Know the database host, port or socket, database name, username, password, and Joomla table prefix. The Recovery Runner can use several database strategies, but it cannot invent hosting-level credentials or permissions.

If you expect the runner to create a database, the supplied account must have permission to do so. If you are replacing an existing prefix or database, understand the confirmation and rollback requirements before starting.

6. Know Whether This Is Same-Site or New-Location Recovery

For the original site, select Recover the original site. For another domain or server, select Restore or move to this domain. New-location recovery uses more conservative destination-preservation behavior and applies additional protection to environment-sensitive server-control files.

7. Gather Administrator and Environment Information

Be ready to validate the Joomla frontend and administrator after recovery. If the administrator is protected by a secret URL parameter, IP rule, WAF, or another access gate, have that normal protected access method available.

Also note environment-specific settings such as HTTPS behavior, absolute tmp/log paths, PHP/server-control rules, mail behavior, caching, and session handling that may differ on another server.

8. Practice Before an Emergency

For important sites, run a recovery test on staging or a disposable target while production is healthy. This exposes missing credentials, insufficient disk space, database-grant problems, path differences, and server-control conflicts before you are working under outage pressure.

Ready-to-Recover Checklist

  • Complete verified Recovery Package.
  • Matching four-digit Recovery PIN.
  • Independent copy/snapshot of destination data you may need.
  • Correct destination Joomla root.
  • HTTPS access when available.
  • Database credentials and required grants.
  • Enough disk space for staging, rollback, and restored files.
  • Normal protected administrator access method.
  • Plan for post-recovery frontend, administrator, routing, and report validation.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCBM feature? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.