Pause and Resume a Running QCBM Backup

QCBM can pause a persistent backup at its saved processing state and later resume the same job. This is safer than killing a PHP request, deleting working files, or launching another Backup Set while the original is still active.

The Pause/Resume control is available from the active manual-backup progress workflow and the active-job controls on the Backups page.

Pause the Active Backup

  1. Open the running backup's progress view.
  2. Click Pause.
  3. Wait for QCBM to save the paused state.
  4. Confirm the active-job display reports the backup as paused.

QCBM preserves the current step, progress percentage, and persistent payload. It also releases the saved backup-create operation lock once the worker reaches the safe control point.

What Pause Does Not Do

Pause does not mark the Backup Set complete, does not verify the Recovery Package, and does not create a new backup. It simply records that the existing job should stop advancing until an administrator resumes it.

Do not manually delete the Backup Set's working directory or database job row while it is paused. Those files and records are what allow QCBM to continue the same work.

Resume the Same Saved Job

  1. Return to the active backup controls.
  2. Click Resume.
  3. QCBM confirms that no worker is still using the job.
  4. QCBM reacquires the global backup-create operation lock.
  5. The job returns to running state and continues from its saved checkpoint.

If another QCBM operation currently owns the required lock, Resume does not force a conflict. The backup remains paused and QCBM tells you to try again after the other operation finishes.

Why Resume May Ask You to Try Again

If QCBM is still reaching the current safe checkpoint, the per-job worker lock may briefly be unavailable. In that case, QCBM reports that it is still reaching the checkpoint and asks you to try Resume again in a moment.

This protects the saved state from being changed while a worker is still writing it.

Avoid Creating a Duplicate Backup

Do not use Create Manual Backup as a substitute for Resume. An unfinished persistent Backup Set should be continued as the same job. Starting overlapping recovery points wastes storage and makes it harder to determine which Backup Set represents the intended operation.

Before starting any replacement run, review the active job and Backup History and confirm the original is truly failed or cancelled.

Pause Versus Postpone

Use Pause when you want the job to remain stopped until you explicitly choose Resume. Use Postpone when you want to save a future resume time; QCBM's Backup Continuation task can automatically resume a postponed job when that time arrives.

Postpone therefore includes timing information that a normal Pause does not.

Verify After Resuming

Once resumed, let QCBM continue through its remaining bounded stages. A successful resume is not the final validation point. Confirm the job reaches complete status, the Backup Set is verified, and the Recovery Package is available.

If the resumed job fails, use the recorded failure phase and message. Do not assume the earlier pause caused the failure unless the evidence actually points there.

When to Use Pause

  • You need to stop heavy backup processing temporarily.
  • You need another QCBM operation to finish before continuing.
  • You want to investigate resource pressure without throwing away the Backup Set's saved progress.
  • You need an intentional administrator-controlled stop rather than a timed Postpone.

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.