Move QC Backup Manager Storage Safely

QC Backup Manager records paths to manifests, database dumps, archive parts, and other managed files. Moving the storage folder outside QCBM can therefore leave healthy files pointing to old database paths.

Use Move Backup Storage when you need to relocate Managed Private Storage. QCBM's migration process copies and verifies the data first, then updates the recorded paths only after the target has passed its safety checks.

Before You Move Storage

  • Finish any active backup, export, deletion, retention, recovery, File Valet, or other QCBM operation.
  • Choose an absolute path to a dedicated folder outside the Joomla document root.
  • Use a new or empty target folder. Do not point the migration at an unrelated directory that already contains files.
  • Make sure the hosting account has enough space for a complete copy of the current managed storage while the migration is in progress.

QCBM refuses to start a storage move while another managed operation is active.

Start Move Backup Storage

  1. Open Components > QC Backup Manager > Settings.
  2. In Managed Private Storage, open Advanced Storage Tools.
  3. Under Move Backup Storage, enter the new protected storage path.
  4. Review the confirmation prompt and start the move.
  5. Leave the operation alone until QCBM reports its result. Do not rename, delete, or edit files in either storage location while migration is running.

What QCBM Does During the Migration

QCBM validates the target before copying data. During the copy it refuses symbolic links and verifies every copied file by comparing both file size and SHA-256 checksum.

For Backup Sets with readable manifests, QCBM updates stored paths inside the copied manifest and calculates the manifest's new SHA-256 checksum. Only after the file work has completed does QCBM update its database paths and active storage setting inside a database transaction.

If a historical Backup Set has a missing or invalid manifest, QCBM preserves the history but can mark that Backup Set as missing instead of pretending it remains a valid recovery point.

What Happens to the Old Folder

After the target is verified and the database transaction succeeds, QCBM attempts to remove the copied top-level items from the old managed folder. If some source items cannot be removed, the migration can finish with a warning so you can review the old folder manually.

Do not delete the old folder yourself before QCBM reports that the active path has switched. If migration fails before the database transaction completes, QCBM is designed to keep the original active path and remove partial copied data where possible.

Verify the New Storage

  1. Return to Status and review Storage Health. The configured path should be the new outside-webroot location.
  2. Confirm QCBM reports the storage as writable and outside the public Joomla document root.
  3. Open Backup History and verify that retained Backup Sets still have usable managed paths.
  4. Create a small controlled Backup Set using a normal Profile.
  5. Verify that Backup Set and confirm its Recovery Package can be downloaded.

The move is not fully proven until a new backup can be created, verified, and retrieved from the new location.

Do Not Move Managed Storage Manually

FTP, a hosting file manager, rsync, or an SSH mv command can move the files but cannot safely update every QCBM database path and manifest relationship. Always use the built-in migration when the existing storage is readable.

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.