Resolve File Conflicts When Retrieving Parked Files

When File Valet retrieves a parked package, an original path may already contain a local file. QCBM makes that conflict an explicit choice rather than overwriting the local file automatically.

Choose the rule in the Retrieve Parked Items dialog before starting retrieval. The same rule is applied wherever an existing file is encountered during that retrieval attempt.

Keep the Existing File and Rename the Retrieved Copy

This is the default. QCBM keeps the current local file untouched and restores the parked copy beside it with a timestamped name such as filename_Retrieved_20260927-173000.ext. If that name already exists, QCBM adds a numeric suffix.

Use this when both versions may matter and you want to compare them manually before deciding which one to keep.

Keep the Existing File and Skip the Parked Copy

QCBM leaves the current local file unchanged and does not restore the conflicting parked copy. Skipped files keep the File Valet item active as Partially Retrieved so the unresolved parked content is not silently discarded.

Replace the Existing File with the Parked Copy

QCBM first copies the existing destination file into a protected retrieval-rollback folder inside the File Valet job storage. It then restores the parked file and verifies the restored SHA-256 checksum.

Use Replace only when you intend the parked version to become the active Joomla file.

Replace Only When the Parked Copy Is Newer

QCBM compares modification times. If the existing local file is the same age or newer than the parked entry, the parked copy is skipped. If the parked entry is newer, QCBM protects the existing file in rollback storage before replacing it.

This rule is useful when timestamps are trustworthy and the parked package should win only when it clearly represents the later version.

Understand the Protected Rollback Copy

The rollback copy is File Valet’s safety record for a file it replaced during retrieval. It lives in the protected private job folder, not beside the public Joomla file. Do not manually remove the File Valet working folder while a retrieval result still needs review.

How Conflict Choices Affect Completion

A renamed file is treated as successfully restored and verified. A skipped file leaves the job partially retrieved because the parked version was not returned. Copy or checksum failures also keep the record active and report the affected path.

Review a Partially Retrieved finding before retrying so you do not unintentionally apply a different overwrite decision to important files.

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.