| 2011-03-27 19:49:12 |
ceg |
bug |
|
|
added bug |
| 2011-03-27 20:43:44 |
Mechanical snail |
bug |
|
|
added subscriber Mechanical snail |
| 2011-03-29 13:55:28 |
ceg |
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.
Names would be stored with the backup files and in the cache.
URLs could be cached.
If full/incremental/restore is called only with a --name option (and a --with-last-options switch?), duplicity could use the cached URLs and settings.
* The cache name would not contain a hash of the url, and stay valid if url changes.
* Named backups could be simply be renamed. |
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.
URLs etc. could be cached for 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.
... |
|
| 2011-03-29 14:06:19 |
ceg |
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.
URLs etc. could be cached for 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.
... |
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.
... |
|
| 2011-04-04 02:25:09 |
Michael Terry |
bug |
|
|
added subscriber Michael Terry |
