[reposting directly to the list, as it seems postings sent via Gmane
disappear into a black hole somewhere...]
I've been using duplicity for a while now, having first tried it about a
year ago and having recently come back to it. Here is a brief wishlist
of features that would make it work much better for me. Hopefully
someone will find this useful.
-- Store local copies of manifests and signature files. These files do
not change and their size still makes it acceptable to cache them
locally. It would speed the backup process immensely if I could tell
duplicity to just keep them stored locally as well, and only download
from the server when the local copies are missing.
-- Provide some way to recover from an aborted first backup, or provide
a way to do this first backup in stages. I have a 50GB filesystem I
need to backup and 50GB of space on another continent where I'd like
this data to land. I can't use duplicity for that. There is simply no
way to do the first backup without it being interrupted by something
-- a network glitch, usually. As it stands now, I simply cannot
backup that data.
Other than that duplicity works very well for me (for smaller backups)!
--J.
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk