QC Backup Manager Requirements and First-Time Setup

QC Backup Manager is designed to give Joomla administrators a repeatable backup and recovery workflow rather than a single one-click archive. A dependable first setup means confirming the server can support the extension, making sure QCBM has protected working storage, setting the Recovery PIN, creating an initial Backup Set, verifying it, and downloading the resulting Recovery Package.

This guide walks through that first setup from installation to the point where you have a verified recovery artifact stored away from the site.

Before You Begin

Before you rely on QC Backup Manager for a production Joomla site, confirm the environment is ready for backup and recovery work.

  • Joomla: use a supported Joomla 4, Joomla 5, or Joomla 6 installation.
  • PHP: use PHP 8.1 or later together with the PHP extensions required by Joomla and by any archive or remote-storage method you plan to use.
  • Administrator access: use a Joomla administrator account with permission to manage QC Backup Manager. Scheduled protection also requires permission to work with Joomla Scheduled Tasks.
  • Disk space: leave enough free space for temporary working data, archive creation, split parts when used, and the final Recovery Package. A Full Backup can temporarily require substantially more space than the finished package.
  • Private storage: QCBM should have a writable Managed Private Storage location. Outside-webroot storage is preferred whenever the hosting account provides a safe writable ancestor.
  • Recovery planning: know where you will keep at least one Recovery Package away from the server being protected.

Open QC Backup Manager and Review Status

  1. Sign in to the Joomla administrator.
  2. Go to Components > QC Backup Manager.
  3. Open the Status tab.
  4. Review the Current Entitlement, Installation, Backup Health, Extension Update, and readiness information before making other changes.

Basic functionality remains available without paid entitlement. If this site should use Pro, Max, or All Access features, authorize the domain in your QuantaCade account and then use Refresh Entitlement on the Status tab.

Do not treat an unexpected tier as a reason to reinstall the extension. First verify the Authorized Domain and entitlement status. Reinstalling does not replace the need for a valid current entitlement.

Confirm Managed Private Storage

Open Settings and review Managed Private Storage. QCBM prefers to place backup and working data outside the public Joomla document root. This reduces the chance that backup archives, manifests, locks, or working packages can be downloaded directly through the website.

If QCBM reports an inside-webroot or compatibility-storage condition, do not manually drag or rename the managed folders. Use the built-in Advanced Storage Tools when a verified storage move is required. Existing Backup Sets and their recorded paths need to stay synchronized with the files on disk.

For large sites, also review the Large Site Readiness information on Status. Storage capacity and writable working space matter before the first large Full Backup, not after it has already started.

Set the Four-Digit Recovery PIN

  1. Remain on Settings.
  2. Find the Recovery Security section.
  3. Enter exactly four digits for the Recovery PIN.
  4. Enter the same four digits again to confirm it.
  5. Save the settings.

QCBM assigns the configured PIN to newly created Backup Sets. Changing the current PIN later affects future Backup Sets only; an existing Recovery Package continues using the PIN assigned when that Backup Set was created. Store the PIN securely with your recovery records.

Review the Included Backup Profiles

Open Profiles. A new QCBM installation includes three core backup profiles:

  • Full Backup - Database and Files for complete-site protection.
  • Database Only for database-focused protection and a smaller first processing test.
  • Files Only for filesystem-focused protection.

Profiles are reusable rules. They determine the backup type and can also control archive behavior, exclusions, schedules, retention, and automatic export when those features are available to the current tier.

Create Your First Backup Set

For a first operational check, a Database Only backup is often a practical starting point because it confirms storage, job processing, manifest creation, and verification with less data than a Full Backup.

  1. Open Backups.
  2. Under Create Manual Backup, enter an optional descriptive title such as First QCBM Test.
  3. Select a published Profile.
  4. Add optional notes if you want the reason for the backup recorded in history.
  5. Click Create Manual Backup.
  6. Allow the staged backup workflow to complete.

Do not start a second backup simply because the browser appears slow or a request is interrupted. QCBM uses persistent job state and operation locks. Check the active job and Backup History before assuming the server-side work failed.

Verify the Backup and Download the Recovery Package

A completed backup is not the final checkpoint. Confirm the Backup Set is verified. Verification checks the stored package information, including expected files, sizes, manifest data, and checksums.

After verification, download the Recovery Package. The package contains the standalone Recovery Runner, recovery instructions, manifest, and the backup data required for that Backup Set. Store the package somewhere separate from the Joomla server.

A backup strategy is much stronger when you have tested a Recovery Package before an emergency. Use a disposable or staging destination for the first recovery test rather than waiting until the production site is unavailable.

Recommended Next Steps

  • Create a Full Backup before Joomla core, extension, template, PHP, hosting, or migration changes.
  • For Pro or higher, create and test an off-site Export Destination before enabling automatic export.
  • If you want scheduled protection, configure the Profile schedule and verify the QCBM Scheduled Tasks are healthy.
  • Keep at least one recent verified Recovery Package somewhere outside the protected server.
  • Read the recovery instructions while the site is healthy and document where your hosting and database credentials are kept.

Common First-Setup Mistakes

  • Skipping verification: a completed job and a verified recovery point are not the same thing.
  • Keeping every copy on one server: a server or account failure can take the website and local backups with it.
  • Moving QCBM storage manually: use QCBM storage tools so database paths and files stay synchronized.
  • Forgetting the Recovery PIN: record the PIN associated with important Backup Sets and protect it from unauthorized access.
  • Assuming a schedule is active without checking Joomla Scheduled Tasks: the Profile schedule and Joomla task health both matter.

Community Discussion

Want to compare backup workflows, share practical tips, or discuss how you use QCBM? Visit the QC Backup Manager Community. For private support, bug reports, or feature requests, use the QuantaCade support system.