copy fails if there is an error reading the destination folder about backupy HOT 1 CLOSED

Thanks for reporting this!

I was able to replicate a similar issue using permissions, however in your case it looks like the folder is corrupted.

I'm still thinking about the best way to handle this, if the unreadable folder is the destination for a backup or mirror, any files that were there will simply show up as missing, and trying to copy anything back there from the source will simply result in failed transfers for those files.

However if the unreadable folder is in the source for a mirror, or either side for a sync with deletions, these files will appear as being deleted and a user not paying attention to the diff could now lose their backup.

For this reason I think it is safer for BackuPy to throw an error and quit without doing anything. I'm still going to think about this for a bit but I'll likely just catch this error and print a more user friendly message then quit.

If you want it to continue running and just ignore this unreadable folder, you can add it to your config by setting filter_exclude_list = ["_X"] or from the command line with --fe "_X" (note I just fixed a bug with filters #5)

from backupy.