Re: [Duplicity-talk] incremental backups only?

[Kenneth Loafman]

Hi,

Long strings of incremental backups are subject to failure if one of the incrementals is corrupted.  I normally do full backups once a week and incrementals on the other days.  You might stretch that to two or three weeks, depending on the reliability of your storage provider, but I would strongly suggest at least two full, verified, backups at all times if you go the long-string route.  You can always remove the incrementals once the next backup and verification is done.

...Thanks,

...Ken

On Mon, Mar 20, 2017 at 9:50 AM, Raphael Bauduin via Duplicity-talk <address@hidden> wrote:

Hi,

I'm using duplicity for backuping a jenkins instance. It is basically a dataset that only grows, with nearly no change to already backed up data as only builds are added and old builds are not changed, leaving only config files as potentially changing.

The data represents a big chunk of our backed up data, and doing a full backup will double the data usage of the jenkins backup, possibly putting us over quota if we keep multiple full backups....

What is the best backup strategy for such a dataset? Is incremental-only a viable option? What are the costs of incrementatl only regarding data safety and restore/verification speed?

Thanks

Raphaël

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk