This guide will walk you through Backblaze buckets and keys, how to set up an S3 Compatible Object Storage Repository pointing to your Backblaze B2 bucket with Immutability, and assigning that repository to a new Backup Job. Is anyone else here using or considering Backblaze (or AWS) for their PRIMARY Veeam repo? One of my primary concerns in all of this is the immutability and the S3 object lock looks like a game changer.With the release of Veeam Backup and Replication Version 12 comes the ability to tier your Veeam Backup Jobs directly to B2 Cloud Storage. I do not think B2’s fireball is an option for us in this instance (object). With B2 that is not possible and we would be downloading TB’s of backup via Object storage.
The cloud connect part is nice since we can get an external drive overnighted in the event of a major outage and he ability to spin up VM’s in the cloud. If all goes well in testing we might I might be pushing 20TB of storage via several customers using the Veeam capacity tier to replace the veeam cloud connect partner IN SOME instances. #2) How has reliability been with backblaze and object storage? #1) How has ingress and egress performance been with backblaze?
I have a test 10GB account and it seems to work well.
Wasabi does not yet support object lock so I am looking at BackBlaze. However, Veeam 10 has added the ability to use S3 copy mode in their capacity tier as well as the support of immutable backups via S3 object lock. For smaller sites I use MSP360 with Wasabi which has been great as well. Basically, I have using Veeam at several of our customers and have been using a Veeam Cloud Connect partner which has really been great. So I know has mentioned backblaze in the past and I am curious what everyone’s current opinion is of their B2 storage.
0 kommentar(er)
