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? 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. 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. 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. MinIO supports lightweight SDKs for Amazon S3 compatible APIs. Once you have configured mc, you can use subcommands like ls, cp, mirror to manage your data. mc config host add myb2 b2_account_id b2_application_key It supports filesystems and Amazon S3 compatible cloud storage services. Command-line Accessĭownload MinIO client (mc) which provides a modern alternative to UNIX coreutils such as ls, cat, cp, mirror, diff etc. To test your setup, point your browser to Use the same B2 credentials to login and access your data. Once you have the account id and application key, export them as environment variables. Once you have downloaded the binary, please follow the guide to create an account on to obtain your account id and application key for B2 storage.
Backblaze support install#
Source is available at Install on Linux amd64 wget
This way you can simultaneously use both Amazon S3 and B2 APIs without compromising any features. S3 object layer is transparent to the applications which use S3 API. MinIO internally translates all the incoming S3 API calls into equivalent B2 storage API calls, which means that all MinIO buckets and objects are stored as native B2 buckets and objects. We added experimental support for Backblaze B2 backend in MinIO to add S3 compatible API support for their B2 service. We also heard from Backblaze team that they are actively expanding their B2 cloud storage service. B2 is competitively priced and has a huge fan following. Some our community members have repeatedly asked for Backblaze B2 Cloud Storage and MinIO integration.