Create a Manual Joomla Backup with QC Backup Manager

Manual backups are available on every QC Backup Manager plan. A manual run is useful before Joomla updates, extension changes, deployments, imports, hosting work, or any other event where you want a recovery point immediately rather than waiting for a schedule.

The Profile you select controls what the backup contains and how QCBM processes it. The manual-backup screen starts the job; the Profile defines the policy.

Before You Start

Check the basics before creating the Backup Set:

  • Managed Private Storage is writable and healthy.
  • A valid four-digit Recovery PIN is configured.
  • The Profile you want to use is published.
  • There is enough free disk space for the selected backup type and its temporary working data.
  • No conflicting backup job is already running.

For a major Joomla, PHP, hosting, extension, or template change, choose a Full Backup unless you have a clear reason why only one part of the site needs protection.

Open Create Manual Backup

  1. Go to Components > QC Backup Manager > Backups.
  2. Find the Create Manual Backup section.
  3. Enter an optional descriptive title, such as Before Joomla 6.1 Update or Before Membership Import.
  4. Select a published Backup Profile.
  5. Add optional notes that explain why the recovery point was created.
  6. Click Create Manual Backup.

Descriptive titles and notes are worth the few seconds they take. During a recovery incident, Before PHP 8.4 Change is more useful than an unlabeled backup created on the same day as several others.

What the Selected Profile Controls

The selected Profile can determine:

  • whether the Backup Set is Full, Database Only, or Files Only;
  • archive and split-archive behavior;
  • folder and extension exclusions;
  • retention policy;
  • automatic off-site export after successful verification, when enabled and available.

Review the Profile before the job if you are not sure what it contains. Starting a manual backup with the wrong Profile can produce a technically successful package that does not contain the recovery data you intended to protect.

Understand Staged and Resumable Processing

QCBM performs backup work in bounded server-side stages instead of assuming one browser request can scan, archive, checksum, and package a large Joomla site from start to finish.

Depending on the backup type and site size, the job can move through work such as database dumping, file enumeration, archive creation, split-part processing, manifest generation, checksum generation, verification, and Recovery Package construction.

This staged design is important on shared hosting and large sites because PHP execution limits, browser timeouts, and network interruptions are normal constraints. QCBM persists job state so supported work can continue safely rather than starting over blindly.

Keep the Progress Workflow Open

During an ordinary manual run, allow the active progress workflow to continue. If QCBM offers the supported Continue in Background path, use that feature rather than closing the browser and assuming the job will finish on its own.

If the browser reports an error or loses the connection, do not immediately launch a second backup. First check:

  • the active backup job;
  • Backup History;
  • the last operational message;
  • whether QCBM reports a running lock or resumable state.

QCBM intentionally prevents conflicting backup work. Starting repeated jobs while one is already active can make troubleshooting harder.

Pause, Resume, Postpone, or Cancel When Needed

Current QCBM backup processing can expose controls for pausing/resuming an active job, postponing work, or canceling it safely. Use those controls rather than terminating files or database records manually.

After a cancel or interruption, return to Backup History and confirm the final status before deciding whether to clean up or create a replacement Backup Set.

Confirm the Backup Set Completed

When the job finishes, review the new Backup History entry. A successful record should identify the Backup Set, Profile, backup type, run source, status, duration, size, storage location, and other recorded details.

A completed status means the backup workflow reached its end. It does not by itself replace verification.

Verify the Backup Set

Make sure the Backup Set is verified. Verification checks that the expected package and manifest are present and that recorded sizes and checksums match the files QCBM saved.

If verification fails, do not treat the Backup Set as a dependable recovery point. Read the failure information, check whether required parts are missing or changed, and create a fresh Backup Set if the site is still healthy.

Download the Recovery Package

For an important manual recovery point, download the canonical Recovery Package after verification and store it somewhere separate from the Joomla server.

Record the Recovery PIN assigned to that Backup Set. Remember that changing the current site PIN later does not change the PIN already attached to an existing Recovery Package.

Manual Backup and Off-Site Export Are Separate Results

If the selected Profile is configured for automatic off-site export, QCBM first needs a successful verified local Backup Set. The remote export happens afterward.

A remote export failure does not automatically invalidate the local Backup Set. Review the local backup and export results separately so you do not delete a valid local recovery point merely because a cloud or remote destination needs attention.

Good Times to Create a Manual Backup

  • before Joomla core updates;
  • before extension or template upgrades;
  • before changing PHP versions;
  • before hosting or DNS migration work;
  • before a large content, user, order, or membership import;
  • before custom development deployment;
  • before removing a major extension or data set;
  • whenever you want a labeled recovery point outside the normal schedule.

Before You Proceed with the Risky Change

Do not stop at “backup completed.” For an important change, confirm:

  • the Backup Set is complete;
  • verification passed;
  • the Recovery Package can be downloaded;
  • the Recovery PIN is recorded;
  • at least one copy exists somewhere other than the server you are about to change.

Community Discussion

Want to compare manual-backup workflows or pre-update practices? Visit the QC Backup Manager Community. For private support, bug reports, or feature requests, use the QuantaCade support system.