Test the Recovery Target and Database Before Starting QCBM Recovery

QCBM provides two preflight tests before you start recovery: Test Locked Destination and, when the selected recovery mode includes the database, Test Database.

Run both after Verify Backup and before Recover Site. They are designed to catch path, permissions, free-space, database, prefix, and privilege problems before long-running or destructive work begins.

Test Locked Destination

The target root is always the physical directory containing qcbm-recover.php. Test Locked Destination confirms the runner is located there and that PHP can write to the directory.

QCBM also estimates how much free space recovery needs for protected staging, rollback, and restored data. For recovery involving files, the estimate is based on the package size with additional headroom; QCBM enforces a minimum safety floor rather than assuming the final site size is enough.

If PHP Cannot Measure Free Space

The runner can still report that the target is writable if the server does not expose disk-free-space information. In that case, verify available space in the hosting control panel before proceeding.

Test Database

Test Database opens the configured MySQL/MariaDB connection, checks the chosen database/prefix, and evaluates the selected database strategy.

What the Database Test Checks by Strategy

  • Existing empty database: fails if the selected database is not actually empty.
  • Existing database with unused prefix: fails if objects already use the selected Joomla prefix.
  • Create this database if permitted: checks whether the account appears able to create the database when needed.
  • Replace selected prefix: reports how many objects use the prefix and confirms they will be saved to protected rollback SQL before replacement.
  • Drop every table and view — Advanced: reports the current object count and confirms the database will be protected by rollback SQL before full cleanup.

Do Not Treat a Passing Connection as Permission to Ignore Scope

A successful database connection proves credentials/connectivity, but you must still read the test message and confirm the destructive scope is what you intended. A passing test for Drop every table and view is not a recommendation to use it.

Fix Failures Before Recover Site

Do not start recovery with unresolved preflight failures. Correct the target directory, disk space, database credentials, grants, database name, prefix, TLS files, or strategy and run the test again.

Preflight Checklist

  • Verify Backup passed.
  • Test Locked Destination passed.
  • Free space is adequate or independently confirmed.
  • Test Database passed when database recovery is included.
  • The database test message matches the intended scope.
  • Required destructive confirmation phrases are understood before recovery starts.

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.