Re:A performance comparison of Duplicacy, restic, Attic, and...
by willvarfar on Tuesday July 18, 2017 @01:42PM
(#14798536)
Classic source control had this problem.
The clever trick is to reencode the previous most-recent backup as a delta from the current state, and do a full-backup of the current state, rather than encoding each new backup as a delta from the previous state (which becomes slower and slower to compute, the more previous states you have).
Problem solved :)
Re:A performance comparison of Duplicacy, restic, Attic, and...
by tatersolid on Wednesday July 19, 2017 @02:17PM
(#14806543)
That's really expensive when your previous backup is on cloud storage
Re:A performance comparison of Duplicacy, restic, Attic, and...
by willvarfar on Wednesday July 19, 2017 @04:23PM
(#14807565)
To compute a delta, you need the previous version. If this previous version is computed from a single file - the previous snapshot - then that's actually less data and effort than if its computed by taking an old snapshot and replaying all the deltas upto the current time.
Yes and no. Duplicity has the "--full-if-older-than" option so you can do incrementals normally, but if your previous full is older than whatever interval you define, it will do a full backup, without changing the command line. So that can be e.g. in a cron job.