Reset QC Backup Manager to the Default Storage Location

Reset to Default Storage restores QCBM's Managed Private Storage setting to the location QCBM currently considers its default. It is intended for a bad, stale, missing, or otherwise unusable configured storage path—not as a shortcut for bypassing the normal storage-migration safeguards.

The reset behaves differently depending on whether QCBM can still read the current storage folder.

Open the Reset Tool

  1. Open Components > QC Backup Manager > Settings.
  2. Open Advanced Storage Tools in the Managed Private Storage section.
  3. Review the path shown beside QCBM default.
  4. Choose Reset to Default Storage and confirm the action.

Do not run the reset while another QCBM operation is active. QCBM checks its operation locks and refuses the reset when managed work is already in progress.

When the Current Storage Folder Is Readable

If the current storage path exists and is readable, QCBM does not simply change a setting and abandon the files. When the default is a suitable outside-webroot location, QCBM uses the same verified migration process as Move Backup Storage: files are copied and checked, recorded paths are updated transactionally, and the active path changes only after the migration succeeds.

If QCBM's current default resolves to Compatibility storage inside the Joomla installation while the existing storage folder is still readable, QCBM will not strand the existing files by switching the path without a verified outside-webroot migration. In that case, keep the current storage or use Move Backup Storage with a suitable outside-webroot target.

When the Configured Path Is Missing or Unreadable

A different recovery path is used when the saved source cannot be read—for example, a stale path from a different server or an invalid foreign drive-letter path after a migration between operating systems.

QCBM prepares its default location, performs filesystem checks, installs the managed storage protection files, and checks direct web access when necessary. If those checks pass, it switches the active storage setting to the default.

Because the old source cannot be read, no old files are claimed to have been moved. Historical Backup Set rows are preserved as evidence rather than silently rewritten or deleted.

What QCBM Uses as the Default

QCBM prefers an account-level storage location outside the public Joomla document root. If the server cannot provide a writable outside-webroot default, QCBM can use its protected Compatibility storage folder inside the Joomla installation.

If the resulting default is inside the webroot, QCBM records Compatibility storage state and applies its Apache/IIS protection files. A live Direct URL test should be reviewed on Status so you know whether the active server actually denied access.

Verify the Reset

  1. Return to Status and review the new configured storage path.
  2. Check the Storage Health label and Direct URL test state.
  3. If the previous path had already become unavailable, expect historical Backup Set records to remain even when their old files cannot be found.
  4. Create a new controlled Backup Set at the reset location.
  5. Verify the Backup Set and download its Recovery Package.

A successful reset proves that QCBM has a usable active storage location. It does not magically recover files that were already missing from the old path.

Reset Versus Move Backup Storage

Use Move Backup Storage when the existing folder is healthy and you deliberately want to relocate all managed data. Use Reset to Default Storage when the configured location itself is wrong or unavailable and you need QCBM to return to its supported default behavior.

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.