mc config host add myb2 b2_account_id b2_application_key It supports filesystems and Amazon S3 compatible cloud storage services. Once you have configured mc, you can use subcommands like ls, cp, mirror to manage your data. MinIO supports lightweight SDKs for Amazon S3 compatible APIs. With open('my-testfile', 'wb') as file_data: from minio import Minioĭata = client.get_object('my-bucketname', 'my-objectname') You may also use Amazon SDKs to access B2 via MinIO. Please let us know if you have any questions or feedback via or Known Limitationsīackblaze B2 does not support CopyObject and CopyObjectPart API which is rarely used.
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? Though it is possible to emulate this at MinIO layer using GetObject and PutObject it would incur additional costs for data transfer.I did check the file path of one of the errors and the file did not exist in Backblaze. If you have Lifecycle Rules setup to "Keep all versions of the file," files will only be removed when Veeam issues a delete command. 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. Then, Veeam will simply try to delete the file again. This can happen for a variety of reasons, especially with an endpoint like DeleteMultipleObjects. 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. Backblaze B2 may have deleted some of the files, but not necessarily all of them. And the Veeam client has no way to knowing which were deleted and which were not. Therefore, the Veeam client will simply try to delete the objects again. As I mentioned previously, the Backblaze B2 functionality differs a bit from the S3 protocol, and that is why you see the NoSuchVersion error.
0 kommentar(er)
