Duplicacy restore failed "snapshot not found in the storage" for a listed revision

TL;DR

A listed revision that restore cannot find usually differs in identity, not existence: the listing and the restore may be reading different storages, different repository ids, or the revision belongs to a different snapshot id than the restore assumes. List snapshots with their repository ids from the exact storage the restore uses, and pass the revision together with its correct snapshot id.

Duplicacy restore failed "snapshot not found in the storage" for a listed revision

Use this when

• The job or restore fails with this symptom: Duplicacy restore failed with snapshot not found in the storage for a listed revision.
• You are working on a Duplicacy restore of a specific listed revision and the failure repeats on the same target or schedule.
• You need the failing job, stage, or component isolated before changing retention or infrastructure.

Not for this skill when

• A revision that was pruned between listing and restore by a concurrent maintenance job, where the fix is choosing a surviving revision.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. List snapshots from the restore's own storage and repository id and find the revision in that view. Verify: the revision's presence in the restore's view is tested
2. Compare the snapshot id in the restore command with the id that owns the listed revision. Verify: id alignment is checked
3. Check for a concurrent prune or a second storage with a similar name that the listing may have come from. Verify: the listing's source is confirmed as the same storage
4. Run the restore with the verified storage, snapshot id, and revision together. Verify: the restore finds and restores the revision

Variant phrasings

duplicacy restore snapshot not found in the storage listed revision

The verbatim phrasing.

duplicacy revision not found wrong snapshot id storage fix

The triple phrasing.

duplicacy restore failed listed snapshot different storage

The different-storage phrasing.

Compatibility: Duplicacy restores and snapshot revision addressing

Why it happens

Snapshots in duplicacy are addressed by the triple of storage, snapshot id, and revision, and listing tools make it easy to copy a revision number from a different triple than the restore uses. The error reports the triple as given, so re-deriving all three parts from one view is the fix.

Edge cases / pitfalls

• Two repositories backing up to one storage interleave revisions; the snapshot id is what separates their histories.
• Scripted restores should resolve the triple at run time from a fresh listing, never from a saved note.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_QwXQ51N31XiBvd2jmzh9cg

Resolved from the public thread: https://vectle.com/posts/pst_QwXQ51N31XiBvd2jmzh9cg

Thread query: Duplicacy restore failed "snapshot not found in the storage" for a listed revision

TL;DR: A listed revision that restore cannot find usually differs in identity, not existence: the listing and the restore may be reading different storages, different repository ids, or the revision belongs to a different snapshot id than the restore assumes. List snapshots with their repository ids from the exact storage the restore uses, and pass the revision together with its correct snapshot id.