Recover Only Joomla Files with the QCBM Recovery Runner
QCBM can recover only the Joomla filesystem from a Files Only Backup Set or from a Full Backup Set. Files-only recovery does not restore database content, so the existing database must already be compatible with the files you are restoring.
Use this mode when the database is healthy or intentionally preserved, but Joomla core, extensions, media, templates, or other site files need to be restored.
1. Verify the Package
Extract the complete Recovery Package into the intended Joomla root, unlock the runner with the Backup Set PIN, and select Verify Backup. Every required file archive part must pass manifest, size, and SHA-256 verification.
2. Choose Files-Only Recovery
Under Recovery type, choose Recover the site files for a Files Only package or Recover only the files when using a Full Backup Set.
Because the selected mode does not include database recovery, the runner hides the database-recovery section.
3. Confirm the Locked Joomla Root
The runner writes only inside the physical directory that contains qcbm-recover.php. Review the displayed Locked Joomla root and select Test Locked Destination.
If the package is in the wrong directory, stop and place it in the correct Joomla root rather than trying to redirect recovery with a form field.
4. Choose the Destination File Strategy
Keep destination-only files and overwrite matching files preserves files that exist only on the destination while restoring matching paths from the Backup Set.
Clean destination, then restore only this backup moves existing destination content into protected rollback storage before restoring the Backup Set. It requires the exact confirmation phrase DELETE DESTINATION FILES.
5. Review Server-Control File Handling
Review the Server-control files strategy. Same-site recovery can restore backed-up .htaccess, .user.ini, php.ini, and web.config files. Cross-domain or cross-path recovery applies additional protection to source .htaccess rules that may be unsafe at the new destination.
6. Recover and Watch the Staged Process
Review the final summary and select Recover Site. Allow QCBM to complete its staged file work. If recovery pauses, use the runner's retry or rollback controls instead of manually modifying protected staging data.
7. Validate File/Database Compatibility
Open the restored frontend and administrator. Check extension loading, templates, media, routing, uploads/downloads, and any functionality that depends on matching code and database schema.
If the restored files came from a different application state than the preserved database, Joomla or extensions may require database schema updates. Do not assume a successful file copy automatically means the site is application-consistent.
8. Finish the Required Completion Workflow
Confirm the installation, disable the Recovery Runner, clean up unchanged uploaded recovery files, download the finalized Recovery Report, and then select Close.
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.