Prepare QC Backup Manager for Large Joomla Sites

Large Joomla sites stress more than archive size. A dependable backup needs enough working space, readable files, a usable archive engine, a configured Recovery PIN, safe storage, and a processing model that can continue across bounded requests.

QCBM includes Large Site Readiness information and backup preflight checks so you can identify those limits before a large Full or Files Only backup is already under load.

Review Large Site Readiness First

Open Components > QC Backup Manager > Status and review Large Site Readiness. QCBM samples included files using the active exclusions and split-size policy, then recommends whether a normal ZIP or Split ZIP approach is appropriate.

The Status card is a readiness estimate, not a complete rehearsal. If the display scan reaches its safe sampling limit, QCBM warns that the real site may be larger. Actual backup creation performs the full inventory.

Check the Backup Profile

Before the first large production backup, open the Profile you intend to use and review:

  • backup type: Full, Database Only, or Files Only;
  • archive strategy and Split size;
  • excluded folders and file extensions;
  • schedule and retry behavior if the backup will run automatically;
  • retention limits and automatic export settings.

Use Auto for archive strategy unless you have a tested reason to force a format. With ZipArchive available, QCBM can choose Split ZIP when the sampled site size approaches or exceeds the selected split target.

Understand the Disk-Space Requirement

QCBM does not compare free space only to the final compressed archive size. Its preflight estimates database-dump space, archive work, the canonical Recovery Package ZIP, Split ZIP staging when used, and an additional safety margin.

That means peak temporary storage can be significantly larger than the final Recovery Package. If split staging and final storage share the same filesystem, QCBM combines those requirements when checking available space.

Resolve hosting quota or free-space warnings before starting a large backup. A small backup succeeding on the same server does not prove that a multi-gigabyte Full Backup has enough temporary room.

Confirm PHP and Storage Prerequisites

  • ZipArchive: QCBM requires PHP ZipArchive for its canonical ready-to-use Recovery Package ZIP.
  • PharData: required when a Profile uses TAR/TAR.GZ archive handling.
  • Recovery PIN: a valid four-digit Recovery PIN must be configured before QCBM creates a new Backup Set.
  • Managed Private Storage: the folder must pass QCBM's filesystem checks and, if it is inside the webroot, its direct-access protection check.
  • Joomla root: files included in the backup must be readable. QCBM reports unreadable files during preflight.

Why QCBM Uses Bounded and Resumable Work

Large backup jobs should not depend on one PHP web request staying alive long enough to scan the site, dump the database, build archives, checksum files, assemble the Recovery Package, verify it, and perform optional export.

QCBM stages backup work into bounded phases and persists job state so later worker requests can continue the same Backup Set. This reduces exposure to ordinary web-request time limits and makes progress easier to inspect when a large operation needs attention.

Bounded processing does not remove hosting limits. Extremely low process timeouts, hard memory limits, filesystem restrictions, or insufficient disk quota still need to be corrected at the hosting level.

Use a Controlled First Run

  1. Confirm Status and Storage Health are clean enough to proceed.
  2. If this is a new server, start with a Database Only or smaller controlled backup to prove the basic storage and job path.
  3. Run the intended large Profile manually once before relying on an unattended schedule.
  4. Watch Backup History until the Backup Set completes and verifies.
  5. Download the Recovery Package and keep an independent copy.
  6. If automatic export is part of the Profile, verify the local backup and the export result separately.

After the Backup

Review the completed Backup Set rather than treating “job finished” as the only success criterion. Verification, a readable Recovery Package, and a tested off-site copy are more important than raw archive size or speed.

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.