I’m pretty sure it’s a problem on the Storj side, but I’ll report it anyway.
I was backing up to Storj using S3, but I decided to try the storj: storage format, and in order not to have problems, I started a new storage from scratch, using a new key with read-write permissions (which works perfectly fine for all my backups) .
When the first backup is performed, everything is fine, chunks are uploaded and the version file “1” is created in the snapshots folder.
However, when running the next backup, it doesn’t identify the already existing version (!):
INFO BACKUP_START No previous backup found
At the end, it tries to delete (!!!) the file “1” (huh? but he didn’t find it at the beginning?) and receives a permission error (of course!).
INFO UPLOAD_PROGRESS Skipped chunk 16120 size 989960, 2.30MB/s 00:00:01 99.9%
INFO UPLOAD_PROGRESS Skipped chunk 16121 size 1359267, 2.30MB/s 00:00:01 99.9%
INFO UPLOAD_PROGRESS Skipped chunk 16122 size 9514, 2.30MB/s 00:00:01 100.0%
ERROR UPLOAD_File Failed to upload the file snapshots/xxxxxx/1: uplink: permission denied (stream: metaclient: permission denied: no permissions to delete existing object)
I’ve double-checked the key and passphrase.
It looks like something about the “object” associated with the file, perhaps a satellite database issue.
Is it really something on the storj side or am I missing something?