Recover Only a Joomla Database with the QCBM Recovery Runner

QCBM can recover only the Joomla database from a Database Only Backup Set or from a Full Backup Set. Database-only recovery leaves the site's filesystem recovery path inactive and focuses the runner on the selected database, prefix strategy, and post-import validation.

Use this mode when the Joomla files are already correct but the database needs to be restored to the backed-up state.

1. Verify the Recovery Package

Extract the package into the intended Joomla root, unlock it with the Backup Set's four-digit PIN, and select Verify Backup. Every required database part must pass size and SHA-256 verification before you continue.

2. Choose Database-Only Recovery

Under Recovery type, choose Recover the database for a Database Only package or Recover only the database when using a Full Backup Set.

The file-recovery strategy is not used in database-only mode.

3. Review the Destination Purpose

Select Recover the original site when restoring the same environment, or Restore or move to this domain when the database belongs to a new destination. The runner still locks recovery to the Joomla root containing qcbm-recover.php.

4. Configure the Database Connection

Review the database host, port/socket, name, username, password, and Joomla table prefix. For same-site recovery, QCBM can prefill source database settings captured with the Backup Set.

If the database service requires encrypted transport, enable Use encrypted database connection settings and provide the applicable CA/client certificate/key paths.

5. Choose the Database Strategy

The runner offers: Use an existing database with an unused table prefix, Use an existing empty database, Create this database if permitted, Replace every object using the selected table prefix, and Drop every table and view in this database — Advanced.

Choose the least destructive strategy that matches the destination. Original-site recovery defaults to replacing the selected source prefix.

6. Understand Rollback Protection

For Replace every object using the selected table prefix, QCBM saves the matching existing database objects to protected rollback SQL before removal/import. The confirmation phrase is DROP PREFIX TABLES.

Drop every table and view saves the selected database to protected rollback SQL before full cleanup, but it is intended only for a dedicated database and additionally requires DROP ALL TABLES plus the exact database name.

7. Test Before Recovering

Select Test Database and read the result. Fix connection, grants, prefix collisions, TLS, or database-creation problems before selecting Recover Site.

8. Validate Joomla After Import

After recovery, confirm the Joomla frontend and administrator can use the recovered schema and prefix. Check login, extension data, menus/content, and any feature whose state is stored in the database.

Finish the runner's required completion sequence and download the Recovery Report before Close is enabled.

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.