Yes, same error on same file after removing it from the source drive. The error is thrown only a few minutes after the backup is started. Perhaps the check is consistency between local and remote databases and hasn’t even looked at the file set yet?
When I created the backup set, I started with a subset of the filesystem branch I was following. It completed successfully, so I selected the entire branch and let it run. It’s been performing the backup for the past month with a couple of glitches that were solved by a repair and continue. This is the first repair/continue cycle that didn’t help. I mention all of this because the files that show as available to restore are only those from the last complete backup run. All those added since are not showing in the listing.