Recover a Complete Joomla Site with the QCBM Recovery Runner

A Full QCBM Backup Set can recover the complete Joomla site—files and database—in one protected Recovery Runner workflow. The runner verifies the package, locks the destination root, tests the database, creates rollback state for destructive choices, performs staged recovery, and then requires post-recovery validation.

Use this procedure when you intend to restore both the Joomla filesystem and database from the same verified Full Backup Set.

1. Unlock and Verify the Full Backup Set

Extract the Recovery Package into the intended Joomla root, open the runner, enter the package PIN, and select Verify Backup. Do not continue unless every required part passes the manifest size and SHA-256 checks.

2. Choose What to Recover

Under 1. Choose What to Recover, select Recover the complete site. This option is available when the package came from a Full Backup Set.

Choose Recover the original site for same-site recovery or Restore or move to this domain when recovering to another domain/server.

3. Test the Locked Destination

Review the Locked Joomla root. It is the physical directory containing qcbm-recover.php and cannot be changed in the form. Select Test Locked Destination before continuing.

QCBM also checks available space because protected staging, rollback data, and restored files may require significantly more room than the final site alone.

4. Choose the Destination File Strategy

For files, choose between keeping destination-only files while overwriting matching files, or the clean-destination strategy that moves existing destination content into protected rollback storage before restoring only the Backup Set.

Clean destination is the default for original-site recovery and requires the exact confirmation phrase DELETE DESTINATION FILES.

5. Configure and Test the Database

Review the captured database settings and the selected database strategy. For original-site recovery, Replace every object using the selected table prefix is the default and creates protected rollback SQL before replacement.

Select Test Database. Do not begin recovery until the credentials, selected database, prefix, and required permissions pass.

6. Review Joomla and Server-Control Choices

Review site name/state, HTTPS, paths, mail/cache/session behavior, administrator-account handling, and server-control file strategy. Cross-domain or cross-path recovery receives additional .htaccess protection because source rules can contain unsafe domain or path assumptions.

7. Review and Select Recover Site

Use the final review summary to confirm the recovery type, destination purpose, file strategy, database strategy, and locked root. When correct, select Recover Site and allow the staged process to run.

If the runner reports a recoverable failure, use its retry or rollback controls rather than manually altering staged recovery files.

8. Complete Post-Recovery Validation

When recovery completes, open the frontend and administrator and resolve any Needs Attention item, including preserved source .htaccess rules when applicable.

Then complete the required order: Confirm Installation, Disable Recovery Runner, Clean Up Uploaded Recovery Files, Download Recovery Report, and finally Close.

What Success Looks Like

The recovered frontend and administrator work, the intended files/database are active, environment-specific warnings have been reviewed, cleanup is complete, and you have downloaded the finalized Recovery Report before closing the runner.

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.