Choose Merge or Clean-Destination File Recovery in QCBM
When QCBM recovery includes site files, the Recovery Runner asks how to handle files already present in the destination. The two choices have very different consequences.
Choose the strategy from the actual condition of the destination—not from convenience during an outage.
The Two File Strategies
Keep destination-only files and overwrite matching files restores files from the Backup Set over matching paths but leaves destination-only files in place.
Clean destination, then restore only this backup moves existing destination content into protected rollback storage first, then restores only the files represented by the Backup Set.
When Merge Is Appropriate
Use the keep/merge strategy when the destination intentionally contains files that are not part of the Backup Set and those files must remain. This is the more conservative choice for many new-location restores.
The tradeoff is that stale or unwanted destination-only files can survive. After recovery, review the final file tree and security-sensitive directories rather than assuming every remaining file came from the backup.
When Clean Destination Is Appropriate
Use clean destination when you intend the recovered site files to replace the destination's existing application content. It is the default for Recover the original site because it avoids leaving unrelated or stale destination files behind.
This is destructive behavior. QCBM requires the exact confirmation phrase DELETE DESTINATION FILES before recovery can start.
How Protected Rollback Works
Before clean-destination restoration, QCBM moves existing destination content into protected rollback storage outside the active site. The recovery package files needed by the runner remain available until final cleanup.
If recovery fails and rollback is available, use the runner's Roll Back Recovery workflow so QCBM can restore protected state in the correct order.
Server-Control Files Are Handled Separately
The file strategy is not the only decision affecting the destination. .htaccess, .user.ini, php.ini, and web.config are governed by the separate Server-control files option and cross-environment safety rules.
How to Choose
- Same-site disaster recovery: clean destination is usually the intended default because the goal is to re-create the backed-up site state.
- New server/domain with destination-specific files: merge may be safer initially, provided you later inspect destination-only files.
- Unknown or contaminated destination: do not choose merge merely to avoid deletion; preserve the destination separately, then use the strategy that produces the clean state you actually want.
Verify After Recovery
After either strategy, confirm the Joomla frontend and administrator, inspect important directories, verify uploads/media, and review any Recovery Report warnings. For merge recovery, specifically look for stale destination-only code or configuration that should not remain.
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.