Choose a Database Recovery Strategy in the QCBM Recovery Runner

The QCBM Recovery Runner offers five database strategies. The correct choice depends on whether the destination database is new, shared, empty, already contains the Joomla prefix you are restoring, or is dedicated entirely to this site.

Two strategies are destructive and create protected rollback SQL before cleanup. Read the consequences before selecting them.

Use an Existing Database with an Unused Table Prefix

Choose Use an existing database with an unused table prefix when the database already exists and you want the recovered Joomla tables imported under a prefix that does not collide with existing objects.

This can be appropriate on hosting accounts that intentionally share one database among multiple applications. Verify that the chosen prefix is genuinely unused.

Use an Existing Empty Database

Choose Use an existing empty database when the target database has already been created and contains no tables/views that need preservation.

The database user still needs sufficient privileges to create and populate the recovered Joomla objects.

Create This Database If Permitted

Choose Create this database if permitted only when the supplied database account is allowed to create the named database. Many shared-hosting environments do not grant this privilege, so create the database in the hosting control panel first when necessary.

Replace Every Object Using the Selected Table Prefix

This is the default for recovery of the original site when QCBM has captured source database settings. QCBM identifies the objects using the selected Joomla prefix, saves them to protected rollback SQL, removes that prefix scope, and imports the backup.

You must type DROP PREFIX TABLES to confirm the operation. Other prefixes in the same database are not the target of this strategy.

Drop Every Table and View in This Database — Advanced

This is the broadest database cleanup option. QCBM first saves the selected database into protected rollback SQL, then removes every table/view and related trigger before importing recovery data.

Use it only for a database dedicated to the site being recovered. It requires the confirmation phrase DROP ALL TABLES and the exact database name.

Protected Rollback SQL

For destructive database strategies, rollback SQL is part of QCBM's recovery safety system. Keep the recovery operation and its protected storage intact until the restored site has been validated.

Rollback protection is not permission to skip an independent destination backup. Preserve valuable data before recovery.

Test Database Before Recovery

After choosing a strategy, select Test Database. The test checks the connection and evaluates conditions relevant to the selected strategy, including existing objects/collisions and required permissions.

Do not select Recover Site until the test result matches what you expect to affect.

Decision Guide

• Shared database, new prefix: unused table prefix.
• Fresh database already created: existing empty database.
• Account can create databases and the database does not exist: create if permitted.
• Same Joomla prefix needs replacement while other prefixes must remain: replace selected prefix.
• Dedicated database should be completely replaced: drop every table and view — Advanced.

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.