Opened at 2009-01-28T21:05:59Z
Last modified at 2010-03-25T02:02:58Z
#597 new enhancement
add 'tahoe sync' command, use backupdb — at Initial Version
Reported by: | warner | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | undecided |
Component: | code-frontend-cli | Version: | 1.2.0 |
Keywords: | usability backup | Cc: | |
Launchpad Bug: |
Description
It would be nice to have a CLI tool which does a minimum-effort copy, from local disk into a Tahoe directory. This tool should behave like "rsync -a --delete": when done, the target directory should look exactly like the local disk's directory. By running the tool on a periodic basis, the Tahoe directory will contain a single most-recent-version backup of the local disk.
tahoe sync ~/music tahoe:my-music
To make this as fast as possible, the default mode will use two assumptions:
- the target Tahoe directory has not been changed by other parties since the last invocation of 'tahoe sync'
- any file changes will modify either their timestamp or filesize
Both assumptions can be disabled with argv flags, at the expense of doing more work. If both assumptions are accepted, then a null backup should require no network traffic and no file reads (only directory reads).
This command would use the 'backupdb', stored in ~/.tahoe/private/backupdb, as discussed in this thread: http://allmydata.org/pipermail/tahoe-dev/2008-May/000620.html . The backupdb would allow the client to quickly determine which files and directories have already been copied.
The proposed "tahoe backup" command would use the same backupdb.