Preview restic restore deletion before reconciling a populated target

Review every proposed target deletion before reconciling an existing directory from a restic snapshot.

Source facts

Restic restore can remove target files that are absent from the selected snapshot when its delete option is used. Include and exclude selections also affect which paths are eligible for that removal. Dry-run mode can report intended restore changes without performing them and checks existing file contents according to the selected overwrite behavior. Directories and symbolic links are always reported as restored in the dry-run listing. A populated target therefore needs a reviewed reconciliation scope.

Source: restic — Restoring from Backup.

Applicability

This applies to the stable restic restore behavior documented here. It addresses optional deletion while restoring into existing content, not permission to replace a live application directory without coordination.

DSE recommendation

DSE recommends restoring to a separate empty staging location for ordinary file recovery. If reconciliation of an existing target is required, capture its present state and review a dry-run listing with the owner before enabling deletion. Keep the selected snapshot, target path, filters, and overwrite policy in one request. Stop the process if any path is ambiguous. Do not make delete a standard recovery wrapper default merely to produce a directory that looks identical to the archive.

Verification

Use a disposable populated target containing both snapshot files and intentional extras. Preview the exact proposed restore and inspect every planned deletion, then compare the actual result in the test copy. Retain the reviewed selection and verify unrelated paths remain untouched before considering an equivalent production change.

Official reference

restic — Restoring from Backup. Reviewed October 15, 2026.