QC Backup Manager Glossary

This glossary defines the terms used throughout the QC Backup Manager documentation so administrators can distinguish backup objects, recovery artifacts, entitlement states, File Valet records, and QCBM Receiver behavior.

The definitions below follow the current QCBM 1.5.13 documentation baseline and intentionally avoid obsolete key-based or removed Reports-tab terminology.

Core Backup and Recovery Terms

Backup Set

A recorded QCBM backup result tied to a Profile, backup type, storage location, verification state, Recovery PIN assignment, and operational history. A Backup Set can produce the portable Recovery Package used by the standalone runner.

Profile

A reusable backup policy. Profiles define Full, Database Only, or Files Only scope and can also control archive behavior, exclusions, scheduling, retry timing, retention, and automatic off-site export.

Full Backup

A Backup Set containing both the Joomla database and site files. It is the normal choice when you need a complete-site recovery point.

Database Only

A backup scope that protects Joomla database objects without archiving the site filesystem.

Files Only

A backup scope that protects the Joomla filesystem without including the database.

Recovery Package

The portable ZIP QCBM prepares for a verified Backup Set. It contains the standalone Recovery Runner, instructions, manifest, and the required database/file backup data.

Recovery Runner

The standalone qcbm-recover.php workflow included in a Recovery Package. It can operate outside normal Joomla routing and guides supported full, database-only, or files-only recovery.

Recovery PIN

The four-digit PIN assigned to a Backup Set when it is created. Changing the current site PIN affects future Backup Sets only.

Manifest

The package record describing the Backup Set and the backup parts/files the Recovery Runner expects, including integrity information used during verification.

Verification

The integrity check that confirms expected package files, recorded sizes, checksums, manifest data, and split parts still match QCBM's recorded Backup Set.

Split Archive

A large archive divided into multiple recorded parts. Every required part must remain available for successful verification and recovery.

Managed Private Storage

QCBM's protected account-level working and backup-storage area. Outside-webroot storage is preferred whenever the hosting environment provides a safe writable location.

Compatibility Storage

A protected fallback storage arrangement used when the ideal outside-webroot path is not available. QCBM can apply additional restrictions or warnings in this state.

Export Destination

A configured off-site target such as Local/Server Path, SFTP, FTPS, FTP, Google Drive, or OneDrive. A destination should pass QCBM's Test before production use.

Default Destination

The off-site destination selected automatically by workflows that use the default rather than an explicitly chosen target.

Automatic Off-Site Export

A Profile option that exports a Backup Set after the local backup has completed and verified successfully.

Retention

Rules that remove eligible old backup artifacts based on Backup Set count or local storage limits. Artifact retention is separate from permanent run history.

Permanent Backup Log

The downloadable CSV backed by QCBM's run ledger. It preserves run-history evidence even when older Backup Set artifacts are removed.

Scheduled Backups

The QCBM/Joomla Scheduled Task workflow that evaluates published scheduled Profiles and starts due backup occurrences.

Backup Continuation

The QCBM task/workflow that can continue supported persisted backup work in the background after a manual job is handed off.

Entitlement Revalidation

The canonical Scheduled Task that refreshes/maintains current keyless Authorized-Domain entitlement health.

Base Tier

The underlying entitlement level associated with the account/site relationship before temporary or broader effective access is considered.

Effective Tier

The QCBM feature tier the current installation can actually use now, considering Authorized Domain, All Access, Max Preview, supported fallback, or Basic.

Authorized Domain

The current QuantaCade mechanism for assigning paid extension entitlement to a Joomla site's domain without requiring normal license-key entry.

30-Day Max Preview

A one-time, manually started 30-day evaluation of Max-level QCBM capabilities on an eligible installation.

File Valet

A Max/All Access storage-management workflow that can find files, build a queue, copy or park files off-site, verify the remote package, retrieve files, and resolve conflicts.

Parked File

A File Valet item whose verified off-site package is intended to be the retained copy after QCBM safely removes the unchanged eligible local original.

File Valet Queue

The reviewed set of selected eligible files/folders that File Valet will package for a Copy Off-Site or Park Files job.

QCBM Receiver

The separate Windows companion that pairs with Max/All Access sites, polls over outbound HTTPS, downloads canonical verified Recovery Packages, resumes interrupted transfers, verifies them locally, and maintains separate local retention.

Receiver Receipt

Receiver-side evidence that a package was downloaded and independently verified, used for deduplication and for workflows that may later remove the hosting copy.

Resumable Download

A transfer that can continue from a prior byte position using HTTP Range rather than restarting from the beginning after every interruption.

Readiness Card

A Status diagnostic focused on a subsystem such as Recovery Readiness, Storage Health, Scheduler Health, Update Delivery, Large Site Readiness, Export Health, or Data Integrity.

Data Integrity Check

A QCBM diagnostic that compares expected records/schema/metadata and can identify safe metadata repairs without treating healthy customer data as disposable.

Recovery Report

The mandatory final report produced by the Recovery Runner summarizing destination choices, database/files work, validation, warnings, rollback, and cleanup state.

How to Use This Glossary

Use the terms above consistently when reading QCBM documentation or opening a support request. For example, say whether a problem affects the Backup Set, the downloaded Recovery Package, the remote Export Destination, or the local Receiver copy. Those are different objects and can have different health states.

Likewise, distinguish completed from verified, and base tier from effective tier. Clear terminology prevents an administrator from troubleshooting the wrong layer.

Version Note

This glossary follows the current QCBM 1.5.13 documentation baseline. Older walkthroughs can contain legacy licensing or interface terms that no longer describe the current customer workflow. Current Authorized-Domain entitlement, the standalone Recovery Runner, the permanent Backup Log, File Valet, and QCBM Receiver terminology should take precedence.

Community Discussion

Need clarification on a QCBM term or want to compare workflows with other administrators? Visit the QC Backup Manager Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.