Set Up Managed Private Storage in QC Backup Manager

Managed Private Storage is the protected working area QC Backup Manager uses for backup data, Recovery Package preparation, staging, locks, and related operations. QCBM prefers an account-level storage location outside the public Joomla document root whenever the hosting environment provides a writable safe ancestor.

Storage location matters because a backup is not useful if its files are exposed to the web, disappear during a migration, or become disconnected from the database records that describe them.

What Managed Private Storage Is For

QCBM uses managed storage for more than the final ZIP file. Depending on the job, the protected storage tree can hold completed Backup Sets, working files, split-archive staging, recovery preparation data, locks, File Valet working packages, and other state needed to resume or verify an operation.

The exact path is hosting-dependent. On a typical hosting account, QCBM attempts to use a writable account-level location outside the Joomla site's public directory. The Settings screen shows the currently configured path as a managed value rather than something you should casually edit by hand.

Why Outside-Webroot Storage Is Preferred

The Joomla document root contains files intended to be served by the web server. Backup data can contain the database, configuration, extension files, private content, and other information that should never be downloadable merely by guessing a URL.

Outside-webroot storage reduces that exposure because the web server is not expected to serve the directory directly. It also keeps backup working data separate from the site tree being backed up.

Outside-webroot storage does not replace off-site protection. A server, hosting-account, disk, or datacenter failure can still affect both the site and an account-level storage folder. Keep at least one verified Recovery Package or off-site copy somewhere independent.

Review the Current Storage Path

  1. Open Components > QC Backup Manager > Settings.
  2. Locate Managed Private Storage.
  3. Review the active path and status information.
  4. Confirm the location is writable.
  5. Open Status and review Storage Health and Large Site Readiness.

If the storage configuration changes, rerun any direct-access or storage-health checks QCBM requests. A healthy path is one QCBM can write to consistently without exposing backup files as public web content.

Compatibility or Inside-Webroot Storage

Some hosting arrangements do not provide a writable safe ancestor outside the public document root. QCBM can have compatibility behavior for protected inside-webroot storage, but it treats that as a condition requiring additional care rather than the ideal layout.

If QCBM reports an inside-webroot warning:

  • review the Storage Health message;
  • run the direct URL protection test when offered;
  • keep verified off-site copies;
  • do not assume a protective server file is equivalent to true outside-webroot isolation;
  • understand that File Valet can refuse to run when its working-storage safety requirements are not met.

Never Move Active QCBM Folders Manually

Do not rename, move, copy, or delete managed QCBM storage folders through File Manager, FTP, SSH, or another tool while backup, export, retention, recovery, storage migration, or File Valet work is active.

QCBM stores paths and operational metadata in the Joomla database. Moving files without updating those records can leave Backup History pointing at the wrong location. Deleting an apparently temporary file can also break a job that was designed to resume later.

Move Existing Backup Storage Safely

When you intentionally need to move storage, use Settings > Advanced Storage Tools > Move Backup Storage.

The managed move workflow is designed to keep file and database state synchronized. Existing Backup Sets are copied to the target location and verified before their recorded paths are changed. Source files are not supposed to be treated as successfully migrated until the verification and path update complete.

Before a move:

  • make sure no backup, export, retention, recovery, or File Valet operation is active;
  • confirm the target is writable and has enough free space;
  • keep an independent Recovery Package for important production sites;
  • do not manually delete the old directory until QCBM reports the migration is complete.

Reset to the Default Storage Location

Use Reset to Default Storage when the configured path is invalid or when you want QCBM to return to its normal managed location.

If the current location is readable, the safest path is a verified migration. If the previously configured location no longer exists or cannot be read, QCBM can restore the default setting without pretending historical files were moved. Older Backup Set records can continue to identify the location where their files were originally expected.

Plan for Disk Space

A Full Backup can require working space for file scanning, database output, archive creation, split parts, checksums, and the canonical Recovery Package. Do not estimate storage only by looking at the final ZIP size.

Before a large operation, review available space at both the Joomla site and the managed-storage location. If the hosting account is near quota, free space first or use an appropriate off-site strategy rather than allowing a large backup to fail midway.

How Storage Relates to File Valet and Recovery

File Valet uses protected working storage while building and verifying off-site packages. QCBM intentionally blocks File Valet when storage safety requirements are not met.

Recovery Packages should be downloaded and stored independently even when local Managed Private Storage is healthy. Managed storage is the site's working backup repository; the portable Recovery Package is what gives you a recovery path that can survive loss of the original server.

Storage Readiness Checklist

  • Managed Private Storage is writable.
  • The path is outside the Joomla document root when the hosting environment allows it.
  • Storage Health does not report unresolved exposure or permissions problems.
  • There is enough free space for the intended backup type.
  • No one is manually moving or renaming active QCBM folders.
  • At least one recent verified Recovery Package exists somewhere independent of the server.

Community Discussion

Want to compare storage layouts or backup-storage practices? Visit the QC Backup Manager Community. For private support, bug reports, or feature requests, use the QuantaCade support system.