reference backups by unique IDs (not url or name)

Bug #743820 reported by ceg
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Duplicity
New
Undecided
Unassigned

Bug Description

The idea is to store the UUID in the backup files, and use it for the name of the cache dir.
Then the correct cache should always be identifyable.
Backup --name option would be stored with the backup files and in the cache.
Time of last backups, URLs etc. could be cached for integrity, informational or convenience reasons.

If duplicity full/incremental/restore is called only with the --name (or an --ID) option, duplicity could use the cached URL(s) and settings.

* The cache name would not contain a hash of the url, and stay valid if url changes.
* Named backups could be renamed without breaking older copies.
...

Revision history for this message
Mechanical snail (replicator-snail) wrote :

Good idea. This will fix a bunch of little annoyances.

Revision history for this message
ceg (ceg) wrote :

Duplicity should inform the user if the backup found at the given url has a known (cached) ID, but is an older copy.

If backing up, proceed updating the backup without interruption.
If restoring, ask the user if he really wants to restore from an older copy.

ceg (ceg)
description: updated
ceg (ceg)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.