Well the Recreate completed, and consistency checks completed, marking database as complete implies the database has been recreated so I’m assuming there are no more “database was attempted repaired, but the repair did not complete” issues.
According to Backups corrupt. How to repair? How can it happen? - #3 by kenkendk the “Invalid header marker” message means the file returned from your destination (in your case the Z: USB drive) didn’t start with an AES header marker.
Your “registering a missing remote file” messages mean the database expected some dblock files on your USB drive but they weren’t included in the list of files found on the drive.
Now that they’re flagged as missing I suspect a database REPAIR (not a recreate) should make those errors go away, but it would be good to first manually check the files really aren’t there - can you check if they’re on the USB drive?
- duplicati-b21e012de23994d60925e4812bef7f2c5.dblock.zip.aes
- duplicati-b3d275f5e20bd4487b78cf828b5d5996b.dblock.zip.aes
- duplicati-b0182911ab75445668b89f1d594d7a1a8.dblock.zip.aes
Are you still getting the “Failed To Decrypt Data” errors?