duplicity-team team mailing list archive
-
duplicity-team team
-
Mailing list archive
-
Message #01809
[Question #237450]: Wrong output of "verify --file-to-restore"
New question #237450 on Duplicity:
https://answers.launchpad.net/duplicity/+question/237450
I' ve duplicity 0.6.18.
I've single changed file in my dir:
$ ls dupl-test/dir/file0
dupl-test/dir/file0
When I've run plain verify:
$ PASSPHRASE=12345 duplicity verify sftp://olimp/backup dupl-test/
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Wed Oct 16 17:09:42 2013
Difference found: File dir/file0 has mtime Wed Oct 16 17:43:44 2013, expected Wed Oct 16 17:15:01 2013
Verify complete: 14 files compared, 1 difference found.
had 1 difference.
But when I run verify for exact file:
$ PASSPHRASE=12345 duplicity verify --file-to-restore dir/file0 sftp://olimp/backup dupl-test/
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Wed Oct 16 17:09:42 2013
Difference found: File . has type dir, expected reg
Difference found: New file dir
Difference found: New file dir/dir1
Difference found: New file dir/dir1/file8
Difference found: New file dir/dir2
Difference found: New file dir/dir2/file9
Difference found: New file dir/file0
Difference found: New file dir/file5
Difference found: New file dir/file6
Difference found: New file dir/file7
Difference found: New file file1
Difference found: New file file2
Difference found: New file file3
Difference found: New file file4
Verify complete: 14 files compared, 14 differences found.
got 14 differences found.
Why it's so ?
--
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.