Understand QCBM File Valet Protected Paths and Storage Requirements

File Valet deliberately refuses Joomla and QCBM paths that could damage the site, expose private working data, or cause File Valet to package its own managed files.

It also requires its private working storage outside the public Joomla document root before a Copy or Park job can start.

Protected Joomla Top-Level Areas

QCBM protects Joomla operating directories including administrator, api, bin, cache, cli, components, includes, language, layouts, libraries, logs, modules, plugins, templates, and tmp.

These directories appear protected in Browse Folders and are filtered from recursive File Valet scans.

Protected Files and QCBM Data

File Valet also blocks important root/server files such as configuration.php, .htaccess, .user.ini, php.ini, web.config, index.php, robots.txt, and related Joomla files.

QCBM recovery runner files, recovery/package names, media/com_qcbackupmanager, and version-control directories such as .git, .svn, and .hg are protected as well.

Local Export Destinations Are Protected

If an Export Destination points to local filesystem storage, File Valet protects that destination from selection. It also protects a path that would contain or be contained by that configured local destination. This prevents recursive packaging of File Valet/backup data.

Symbolic Links, Outside-Root Paths, and Unreadable Items

Symbolic links cannot be selected. A selected path must resolve inside the Joomla site root, and recursive scans keep only readable eligible content. File Valet does not provide a bypass for these safety rules.

If an otherwise ordinary file is unavailable because of filesystem permissions, correct the underlying read access rather than moving it into a protected workflow by force.

Managed Private Storage Must Be Outside the Web Root

File Valet derives its working folder from QCBM Managed Private Storage. The resulting File Valet storage must be an absolute path outside JPATH_ROOT, must be creatable, and must be writable.

If the File Valet Queue shows Move Managed Private Storage first, open Settings → Advanced Storage Tools and move the existing Backup Sets before starting another File Valet job.

Why These Rules Matter

File Valet creates package archives, manifests, download staging files, retrieval rollback copies, and job state that must not be public or accidentally included in a File Valet package. The protected-path and outside-webroot rules keep that management data separate from the Joomla content being moved.

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.