From: pataquets Date: Sat, 7 Jul 2012 17:23:10 +0000 (+0300) Subject: Update adding comments as seen in https://tahoe-lafs.org/pipermail/tahoe-dev/2012... X-Git-Tag: allmydata-tahoe-1.10.1a1~177^2 X-Git-Url: https://git.rkrishnan.org/%5B/%5D%20/uri/frontends/%22doc.html/?a=commitdiff_plain;h=fac1f0d55a7c60dd38fb9c625090833e819cbd50;p=tahoe-lafs%2Ftahoe-lafs.git Update adding comments as seen in https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007365.html Found it useful. I can't see here clearly if deleting backupdb will affect deduplication and I'd like to clarify here, anyway. Do deduplication depend on backupdb data? TIA. --- diff --git a/docs/frontends/CLI.rst b/docs/frontends/CLI.rst index 96927dbe..fa31dcf3 100644 --- a/docs/frontends/CLI.rst +++ b/docs/frontends/CLI.rst @@ -483,15 +483,27 @@ Command Examples snapshot in work:backups/Latest/ . This command uses a small SQLite database known as the "backupdb", stored in ``~/.tahoe/private/backupdb.sqlite``, to remember which local files have been backed up already, and will avoid - uploading files that have already been backed up. 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. + uploading files that have already been backed up (except occasionally that + will randomly upload them again if it has been awhile since had last been + uploaded, just to make sure that the copy of it on the server is still good). + 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 should delete the stale backupdb.sqlite file, to force "``tahoe backup``" 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`` Same as above, but this time the backup process will ignore any