Retrieve Parked Files to Their Original Locations with File Valet

Retrieve returns an active parked File Valet package to the original Joomla-relative paths recorded when the job was created. Missing folders are recreated automatically.

Before any file is restored, QCBM downloads and verifies the package, validates its protected manifest, checks every staged file checksum, and asks how existing local files should be handled.

Start Retrieval

  1. Open QC Backup Manager → File Valet.
  2. Find an item with a Parked, Partially Parked, Partially Retrieved, or retrieval-failed state.
  3. Choose Retrieve.
  4. Under When a file already exists, choose the conflict rule you want.
  5. Choose Retrieve to Original Location.

QCBM Verifies the Package Before Restoring

QCBM downloads the managed package into private File Valet storage and confirms the package size and SHA-256 checksum. It then validates that the embedded manifest belongs to this File Valet record and matches QCBM’s protected saved manifest.

Each staged file is also checked against the checksum recorded in the manifest. Protected or unsafe paths stop retrieval rather than being written to the site.

Original Folders Are Recreated

Retrieval always uses the recorded original location in QCBM 1.5.13. Missing directories are created beneath the Joomla root as needed, and recorded directory/file permissions and modification times are reapplied where possible.

Choose How Existing Files Are Handled

The default option keeps the existing file and gives the retrieved copy a timestamped _Retrieved_YYYYMMDD-HHMMSS name. You can instead skip the parked copy, replace the existing file, or replace it only when the parked copy is newer.

When QCBM will replace an existing file, it first creates a verified rollback copy in the File Valet job’s protected private storage.

Restored Files Are Verified

After copying a staged file into place, QCBM calculates its SHA-256 checksum and compares it with the package manifest. A checksum failure is recorded as a retrieval failure rather than silently completing.

What Happens After Successful Retrieval

When every eligible file is restored without skips or failures, QCBM deletes the managed off-site package, removes the active File Valet database records, and removes the private job folder. The item then disappears from the active File Valet list.

If files fail or are skipped by the selected conflict rule, the item remains active as Partially Retrieved so you can review and retry. If all local files were restored but remote package deletion fails, the item becomes Cleanup Required.

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.