Optionally do incremental backups with rdiff-backup, duplicity, or StoreBackup

[Mike.lifeguard]

While BIT does use hardlinks to reduce disk usage for unchanged files, this offers no efficiency for files that changed a little bit. BIT should optionally use rdiff-backup to store deltas, thereby gaining efficiency for this case.

[Fabrice (fabrice-chtiland)]

This would be great !

Yet the folder I need to back up is >60Gb !
One backup per day makes :
- 420 Gb for One week
- 1 860 Gb for One month !!

With rdiff backup this should use between 100 Mb and 200 Mb per month !

So, I don't use BIT for instance...

[Christoph Buchner (bilderbuchi)]

I have to pipe in here. I just wanted to open a Question if the BIT team is aware of rdiff-backup, but found this bugreport instead. I would also very much like to see rdiff-backup support. I think considerable synergies may be exploited, the use-case is very similar.

[Christoph Buchner (bilderbuchi)]

aaand a link for convenience: http://www.nongnu.org/rdiff-backup/

[ceg (ceg)]

Duplicity uses rdiff-backup but would also bring network and encryption features http://duplicity.nongnu.org/

[ceg (ceg)]

When the backend is set to dublicity, BIT's file/snapshot browser would (just) have to list the contents of a file/command output (duplicity's listing of the snapshot) instead of listing actual directory structures on disk.

[ceg (ceg)]

Found StoreBackup, it creates fully readable snapshots (hardlinked filesystem) and supports small diffs/deltas for large files.

StoreBackup will produce checksums and recognize renamed or moved files (and hardlink them instead of storing them again).
http://www.nongnu.org/storebackup