ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-01-17 10:20:13 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge branch 'pr6'

Browse Source
This commit is contained in:
Brian Warner 2014-07-02 13:11:28 -07:00
commit e61632909c
1 changed files with 16 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/frontends/CLI.rst
View File

@ -483,15 +483,27 @@ Command Examples
snapshot in work:backups/Latest/ . This command uses a small SQLite database snapshot in work:backups/Latest/ . This command uses a small SQLite database
known as the "backupdb", stored in ``~/.tahoe/private/backupdb.sqlite``, to known as the "backupdb", stored in ``~/.tahoe/private/backupdb.sqlite``, to
remember which local files have been backed up already, and will avoid remember which local files have been backed up already, and will avoid
uploading files that have already been backed up. It compares timestamps and uploading files that have already been backed up (except occasionally that
filesizes when making this comparison. It also re-uses existing directories will randomly upload them again if it has been awhile since had last been
which have identical contents. This lets it run faster and reduces the uploaded, just to make sure that the copy of it on the server is still good).
number of directories created. It compares timestamps and filesizes when making this comparison. It also
re-uses existing directories which have identical contents. This lets it
run faster and reduces the number of directories created.
If you reconfigure your client node to switch to a different grid, you If you reconfigure your client node to switch to a different grid, you
should delete the stale backupdb.sqlite file, to force "``tahoe backup``" should delete the stale backupdb.sqlite file, to force "``tahoe backup``"
to upload all files to the new grid. to upload all files to the new grid.
The fact that "tahoe backup" checks timestamps on your local files and
skips ones that don't appear to have been changed is one of the major
differences between "tahoe backup" and "tahoe cp -r". The other major
difference is that "tahoe backup" keeps links to all of the versions that
have been uploaded to the grid, so you can navigate among old versions
stored in the grid. In contrast, "tahoe cp -r" unlinks the previous
version from the grid directory and links the new version into place,
so unless you have a link to the older version stored somewhere else,
you'll never be able to get back to it.
``tahoe backup --exclude=*~ ~ work:backups`` ``tahoe backup --exclude=*~ ~ work:backups``
Same as above, but this time the backup process will ignore any Same as above, but this time the backup process will ignore any