Checks on copy command

towerbr     Mar 16 7:36PM 2018 CLI

I made a copy of a local storage to a Dropbox storage. Then I run the command again to see if any chunk will be copied. The result was expected (nothing to copy) but the command took only a few seconds to execute, and returned that "all snapshots" were there. But what if one or more chunks in the remote storage were lost? I personally do not completely trust any of these providers.

Should not there be an option (similar to -exhaustive in prune) to check the chunks? The loss of only one chunk can invalidate all the backup.


gchen    Mar 16 10:19PM 2018

I think a check -storage dropbox command should accomplish what you want?


towerbr    Mar 17 10:33AM 2018

Sure, but this would have to be done by script, error checking, etc.

Consider that it is a set of backup and copy scripts that run automatically (scheduled).

It would be more practical if it were an option of the copy command itself.

I'll have to do something like this in the script:

duplicacy copy
duplicacy check
if any error occurred
      warn me

(by the way, I didn't find a list of error codes in the documentation, something like this)


towerbr    Mar 17 11:38AM 2018

What a coincidence! Check this post.


gchen    Mar 17 8:51PM 2018

Currently if a snapshot exists in the destination storage, Duplicacy doesn't check its chunks. Maybe a -check option should be added to the copy command. This should be a simple change.


towerbr    Mar 18 2:37PM 2018

Maybe a -check option should be added to the copy command. This should be a simple change.

Exactly! It would be great.