Merge lp:~aaron-whitehouse/duplicity/08-fix-man-verify into lp:~duplicity-team/duplicity/0.8-series

Proposed by Aaron Whitehouse
Status: Merged
Merged at revision: 1238
Proposed branch: lp:~aaron-whitehouse/duplicity/08-fix-man-verify
Merge into: lp:~duplicity-team/duplicity/0.8-series
Diff against target: 48 lines (+18/-7)
1 file modified
bin/duplicity.1 (+18/-7)
To merge this branch: bzr merge lp:~aaron-whitehouse/duplicity/08-fix-man-verify
Reviewer Review Type Date Requested Status
duplicity-team Pending
Review via email: mp+325044@code.launchpad.net

Description of the change

Fix description of --verify and --compare-data in the man page. Now clarifies that verify compares the restored files to hashes stored at backup date, while --compare-data compares restored files to files in target_path.

To post a comment you must log in.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'bin/duplicity.1'
2--- bin/duplicity.1 2017-05-12 21:55:05 +0000
3+++ bin/duplicity.1 2017-06-04 16:35:10 +0000
4@@ -168,17 +168,22 @@
5
6 .TP
7 .BI "verify " "[--compare-data] [--time <time>] [--file-to-restore <rel_path>] <url> <local_path>"
8-Restore backup contents temporarily file by file and compare against the local path's contents.
9-duplicity will exit with a non-zero error level if any files are different.
10-On verbosity level info (4) or higher, a message for each file that has
11-changed will be logged.
12+Verify tests the integrity of the backup archives at the remote location by downloading each file
13+and checking both that it can restore the archive and that the restored file matches the signature
14+of that file stored in the backup, i.e. compares the archived file with its hash value from archival
15+time. Verify does not actually restore and will not overwrite any local files. Duplicity
16+will exit with a non-zero error level if any files do not match the signature stored in the archive
17+for that file. On verbosity level 4 or higher, it will log a message for each file that differs
18+from the stored signature. Files must be downloaded to the local machine in order to compare them.
19+Verify does not compare the backed-up version of the file to the current local copy of the files
20+unless the --compare-data option is used (see below).
21 .br
22 The
23 .I --file-to-restore
24 option restricts verify to that file or folder.
25 The
26 .I --time
27-option allows to select a backup to verify against.
28+option allows to select a backup to verify.
29 The
30 .I --compare-data
31 option enables data comparison (see below).
32@@ -344,8 +349,14 @@
33
34 .TP
35 .BI --compare-data
36-Enable data comparison of regular files on action verify.
37-This is disabled by default for performance reasons.
38+Enable data comparison of regular files on action verify. This conducts a
39+verify as described above to verify the integrity of the backup archives,
40+but additionally compares restored files to those in target_directory.
41+Duplicity will not replace any files in target_directory. Duplicity will
42+exit with a non-zero error level if the files do not correctly verify or
43+if any files from the archive differ from those in target_directory. On
44+verbosity level 4 or higher, it will log a message for each file that
45+differs from its equivalent in target_directory.
46
47 .TP
48 .BI --copy-links

Subscribers

People subscribed via source and target branches