I'm told there are many folks facing exactly the same error and the case is now passed on to Tier 2. The remote session with support could not find the root cause of the error nor fix it. I get that.Īnyway, I have escalated the support request and is getting someone look at the problem over a remote session. Well, its not easy to keep up the quality of support with covid raging, and on top of that its holiday season. Considering the usage 'the ID', probably he confused my case for someone else's. What ID? I never asked how to set any ID and why would I want to set any ID when I'm trying to get help on how to solve the offload error. After an initial exchange over logs and more details, and a few emails back and forth this is all what I receive in a 2 line email:Ī link to some generic docs on use of aws cli utility (which I'm well aware of) for manipulating object lock, saying that his Tier 2 team recommended that I follow those docs to 'set the ID of S3'. Let me try again after having slept over my irritation: I reported an SOBR offload error that has stopped copying of several recent restore points to capacity tier (backblaze). In the B&R console selecting 'Jobs' and 'HISTORY' shows no error (all jobs successful) but selecting 'Storage Management' shows the offload errors, so I failed to notice this for several days. Wonder why no email notification is received for this error. Has that changed? The error (below) refers to some invalid version id.

'keep only the last version' is enabled on the bucket at backblaze end as was the recommended practice prior to immutability support in B2. Immutability is set to 30 days in the B&R object repository and backups are copied to capacity tier as they are created. Now this backup chain seems to have a reached a stage where it has to delete some files in the object storage which errors with a 'DeleteMultipleObjects' failed message (see below). A month ago I changed the capacity tier to use a bucket with object lock when B2 acquired immutability support. The SOBR has a one performance and one capacity tier (backblaze) and has been working fine for a long time. I just found out capacity tier offload of one of my backup jobs has been failing for several days now.

Backblaze log in