TimeVault Could Save Reverse Diffs Rather Than Copy FIles

Bug #159205 reported by Brian Pitts on 2007-11-01
4
Affects Status Importance Assigned to Milestone
TimeVault
Medium
Unassigned

Bug Description

My apologies if I've misunderstood the code, but from snap.py it looks like each time a file changes TimeVault stores a copy of the entire file rather than just the parts that changed. This means that a small change in a large file will cause lots of data to be stored redundantly. It would be nice if TimeVault would only store reverse diffs like rdiff-backup (http://www.nongnu.org/rdiff-backup/ , python, GPL) and would reconstruct the full files when restoring from a backup.

SourceContact (sourcecontact) wrote :

You have not misunderstood the code :). rdiff-backup is a very cool application. Thanks for bringing it to my attention - I have started to look at the code to see if I can incorporate some of the techniques into TimeVault.

Changed in timevault:
importance: Undecided → Medium
status: New → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers