Core Features

• Free Basic plan with a 3-day free trial of all Max features
• Create full-site, database-only, and files-only backups
• Use and edit the three included backup profiles
• Run manual backups from the Joomla administrator area
• Review Backup History and backup status
• Download completed Backup Sets
• Create guided Recovery Packages
• Recover a complete Joomla site with the standalone Recovery Runner
• Verify backup files and review backup health information
• Use staged backup processing for larger Joomla sites
• Edit plain-text Email Templates on Basic
• Delete backup records and stored Backup Sets
• Use server-side safety checks for backup, recovery, Receiver, and license-controlled actions

Pro Features

• Free Basic plan with a 3-day free trial of all Max features
• Create additional backup profiles
• Schedule exact automated backup times
• Configure profile-specific retention limits
• Use one active off-site storage destination
• Export backups off-site manually
• Export backups off-site automatically after completion
• Use HTML Email Templates
• Configure scheduled backup and retention workflows
• Keep saved off-site settings available if the license is later downgraded

Max / All Access Features

QCBM Receiver is included with Max / All Access and turns a Windows computer into a private backup collection and recovery station for your Joomla sites. It can run quietly in the background, pull verified Recovery Packages directly from Joomla to storage you control, maintain local backup retention, and help take a Recovery Package from safe local custody all the way through a guided site recovery.

• Use multiple off-site storage destinations
• Automatically collect backup packages to a Windows computer using QCBM Receiver
• Save Receiver backups to a local folder, external drive, or Windows-accessible network/NAS location
• Manage multiple Joomla sites from one QCBM Receiver installation
• Pair a Joomla site with more than one Receiver when separate backup destinations or devices are wanted
• Keep normal polling and backup collection running through the Windows Service even when the Receiver window is closed
• Connect QCBM Receiver directly to Joomla over HTTPS
• Pair with a short-lived, single-use code instead of storing Joomla Super User credentials in Receiver
• Give each paired Receiver its own device credential, receipt history, and independent revocation
• Automatically detect the newest eligible verified Recovery Package that has not yet been received by that device
• Let Receiver assist QCBM with overdue scheduled backups on quiet sites, using QCBM's own persistent backup engine rather than exposing Joomla's general scheduler
• Pause, resume, or cancel an active Receiver download
• Resume interrupted downloads with HTTP Range support instead of restarting large transfers from the beginning
• Verify the completed local file by expected size and SHA-256 before it is acknowledged as successfully received
• Record verified device-and-backup receipts so the same Recovery Package is not immediately downloaded again
• Optionally delete the hosting copy only after the Receiver has successfully downloaded and verified the Recovery Package
• Apply per-site local retention by maximum age, backup count, and Receiver-managed storage size
• Keep at least the newest successfully verified Receiver-managed backup for each connection
• Protect unrelated files, manually added packages, and active/partial transfers from Receiver retention cleanup
• Use the selected local Backup destination as the live source for available Recovery Packages
• Recover from valid QCBM Recovery Packages that were manually copied into the selected destination folder
• Ignore unrelated/random ZIP files by validating QCBM Recovery Package structure before recovery
• Keep manually added Recovery Packages outside Receiver-managed retention ownership
• Launch one-click Receiver-guided recovery using QCBM's protected Recovery Runner as the server-side recovery authority
• Restore Full, Files Only, or Database Only Recovery Packages using the supported recovery policies
• Use Restore Site for recovery back to the paired Joomla site
• Use Restore to other Location for a guided recovery to a different hosting location without overwriting the original source site
• Configure a separate Recovery Connection using FTP or SFTP without mixing those hosting credentials into normal Receiver pairing
• Verify that the configured remote webroot really maps to the intended Joomla HTTPS site before deploying recovery files
• Revalidate the selected local Recovery Package before recovery deployment
• Upload only the validated recovery payload and launch the Recovery Runner after server-side reachability is confirmed
• Use the Backup Set-specific four-digit Recovery PIN derived from the Recovery Package filename in the Receiver recovery workflow
• Keep the destructive file/database restore engine on the Joomla hosting side, where it can use QCBM's rollback, validation, configuration, health-check, cleanup, and reporting safeguards
• Receive recovery progress and finalization through the Receiver-guided workflow instead of building a separate Windows restore engine
• Use QCBM's final Recovery Report and cleanup/finalization process after restoration
• Store Receiver device secrets and saved recovery credentials using Windows machine-protected DPAPI storage
• Use QCBM Receiver's signed Windows application and verified self-update path
• Access full File Valet storage-management tools
• Copy selected files and folders to verified off-site storage
• Park local files only after the off-site package is verified
• Restore parked files to their original Joomla locations
• Recreate missing original folders during retrieval
• Choose how existing local files are handled during retrieval
• Verify parked packages without reloading the File Valet page
• Delete off-site packages and manage parked-item records
• Review Backup Reports and export supported report data to CSV
• Access Max-level backup, storage, reporting, Receiver, recovery, and File Valet controls

Safety First

QC Backup Manager is designed around controlled backup, recovery, storage, and Receiver workflows. Backup files are created through staged processes, verified before they are treated as complete, and kept separate from normal Joomla content wherever the server configuration allows.

Recovery Packages use a guided standalone Recovery Runner with PIN protection, environment checks, rollback-aware database and file handling, and clear final cleanup steps. File Valet does not remove local files until the off-site package has been created and verified, and parked files are restored to their original locations with configurable conflict handling.

QCBM Receiver uses direct HTTPS communication between the Windows computer and the Joomla site. Pairing uses a short-lived one-time code and creates a unique device credential, so Joomla Super User credentials are not stored in the Receiver. Interrupted transfers can resume, completed downloads are verified before receipt is recorded, and the optional hosting-copy deletion occurs only after the Receiver has successfully downloaded and verified the Recovery Package.

For recovery, QCBM Receiver validates the local Recovery Package, verifies the configured target, deploys the recovery payload, and orchestrates the existing QCBM Recovery Runner. The Recovery Runner remains the server-side authority for destructive file/database work, rollback protection, site validation, cleanup, and the final Recovery Report.

Safety protections are available across the extension, including server-side license enforcement, protected recovery paths, backup verification, resumable processing, Receiver entitlement checks, device revocation, verified-receipt handling, ownership-scoped local retention, target/webroot validation, and audit-friendly history records.