|
From: | Aaron |
Subject: | Re: [Duplicity-talk] how to use verify command? |
Date: | Fri, 5 May 2017 23:10:12 +0100 |
Hello John/Edgar, On 27/03/17 11:47, edgar.soldin--- via Duplicity-talk wrote:
John, right, verify works on the complete backup or a subset given by --file-to-restore . this might not be highly optimized, but is useful as far as you will know if your chain up to now (or time given) is corrupted or not. afaik files marked as deleted will not be restored and checked.. ede/duply.net On 27.03.2017 12:41, John Covici wrote:So, if I do an incremental backup, there is no verify command to just verify the files I just backed up? Otherwise verify is not that useful as it must verify everything.
Yes, Edgar is right. This is actually the topic of an old bug report here: https://bugs.launchpad.net/duplicity/+bug/982902My current feeling is that the existing behaviour is sensible. As mentioned above, you could take note of which files duplicity backed up during an incremental and pass these to --file-to-restore. That would be far safer than just verifying the incremental (if such a thing were possible), as it would also check that the parts of the backup chain that the incremental depended on for those files.
Kind regards, Aaron
[Prev in Thread] | Current Thread | [Next in Thread] |