Hey Andrew (@AP1111),
I took a second look at this and realized that you were backing up the root of a volume. I missed that on the first pass. We are supposed to prevent this from being done in the first place because it can cause some odd behavior (like the permissions issues you are seeing). You should actually get an error if you try to setup a backup like this. Can you walk me through how you set the folder for backup. My testing is hitting the expected error when I try.
Interesting. If you are able to share the exact naming of an item I can reproduce and make sure we are handling the Amazon Drive error properly. I think we may be lumping the exception coming back with another error, which causes more confusion.
There was another user who was attempting this, as well. He was targeting a folder in ~/Library. We were originally rejecting the ~/Library folder, but we removed it in a follow-up release. There is an image in the thread that shows the location he was backing up: Backup feedback - #9 by Tony
The current version actually works on M1’s using Rosetta 2, we just don’t have a native build for it yet. This is something we are going to be looking into, but you should be able to use odrive without an expected issues on M1-based systems right now.