If you are experiencing errors in completing the backup jobs OR if restore/recoveries are failing against backups where this error is found, please let us know.

My understanding is that this error does not cause a backup job from failing. Backblaze is committed to fix this and the log messages will disappear. As I mentioned previously, the Backblaze B2 functionality differs a bit from the S3 protocol, and that is why you see the NoSuchVersion error. Therefore, the Veeam client will simply try to delete the objects again. And the Veeam client has no way to knowing which were deleted and which were not. Backblaze B2 may have deleted some of the files, but not necessarily all of them. As an example, let's say the Veeam client sends a list of 100 objects to delete and before the delete is complete, the Internet connection breaks. This can happen for a variety of reasons, especially with an endpoint like DeleteMultipleObjects. Then, Veeam will simply try to delete the file again. It is possible that Veeam issues a delete command and the delete was successful, but Veeam didn't have the opportunity to record the successful delete. If you have Lifecycle Rules setup to 'Keep all versions of the file,' files will only be removed when Veeam issues a delete command. When you say one of the 'errors' - I assume you mean 'DeleteMultipleObjects request failed to delete object error: NoSuchVersion, message: 'Invalid version id specified'', correct? I did check the file path of one of the errors and the file did not exist in Backblaze.

Backblaze b2 storage