Resume an Interrupted QCBM Recovery

QCBM recovery is staged and journaled so an interrupted browser request, connection loss, or recoverable runtime problem does not require you to start a second recovery from the beginning.

When the same Recovery Runner finds an unfinished protected operation, it presents Unfinished Recovery Found, restores safe non-secret settings, and offers Resume Recovery.

Reopen the Same Recovery Runner

Return to the same destination and the same extracted Recovery Package. Unlock the runner again with the Backup Set's four-digit Recovery PIN.

Do not copy a second package into the destination or start a parallel recovery while the protected operation exists.

Unfinished Recovery Found

The runner reads the protected recovery journal and shows the phase and percentage where the unfinished operation was recorded. Starting a second recovery is blocked while that unfinished state is active.

Review the prefilled choices before resuming so you understand which file/database strategy the existing operation is continuing.

Re-enter Secrets

QCBM deliberately does not persist sensitive values such as the database password or administrator recovery password in the safe resumable input. Re-enter required passwords before attempting to resume.

Other safe settings can be prefilled from the protected operation state.

Resume Recovery

When the form is valid, select Resume Recovery. QCBM continues the staged operation using the protected journal rather than creating a duplicate operation.

If the interrupted state is already in a rollback phase, the runner resumes rollback instead of normal forward recovery.

Retry a Failed Step

If a recoverable step fails, the progress view can offer Retry Last Step. Correct the external cause first—for example permissions, disk space, database connectivity, or a temporary server condition—then retry.

Roll Back When Continuing Is Not Safe

When rollback is available, use Roll Back Recovery rather than manually deleting staging or rollback files. QCBM uses its journal to restore protected database/file state in the intended order.

Do Not Delete Protected Recovery State Mid-Operation

The journal, staging data, locks, and rollback material are part of the resumable safety design. Removing them manually can destroy QCBM's ability to identify what completed and what still needs to be restored or rolled back.

After Resume Completes

Validate the frontend and administrator, resolve any Needs Attention item, then follow the normal finalization order: confirm installation, disable the runner, clean up unchanged uploaded package files, download the Recovery Report, and Close.

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.