VBR: Immutable object storage with Wasabi


Userlevel 7
Badge +6

Inspired by @Geoff Burke‘s post about immutability for Kasten with Wasabi, I decided to post the same for Veeam Backup & Replication. If you want to check out Geoff’s post, then follow this link:

What/who is Wasabi?

Probably Wasabi doesn’t need to be introduced. But if you can only think about the paste you get with Sushi, then you should check out their cloud object storage. Besides AWS and Microsoft, Wasabi is one of the Vendors, who often gets recommended for usage with Veeam Backup. The reason for that is their really competitive pricing, combined with great functionality/quality and low complexity.

How to create an immutable bucket

After registering an account with Wasabi, the creation of an immutable bucket isn’t complicated at all.

Just make sure that you select the right region for your location, and also enable bucket versioning and object locking.

Afterwards you need to create an access key. For testing purposes you can use the root account key, but for production you should create a dedicated user with limited permissions. I’ll write a separate post about this in the next time.

Add Wasabi to Veeam

Next you need to add the newly created bucket as a S3 compatible object storage repository.

 

Depending on the region you have selected, you will have to use a specific service point/URL. Visit this site to find out the corresponding URL: https://wasabi-support.zendesk.com/hc/en-us/articles/360015106031-What-are-the-service-URLs-for-Wasabi-s-different-storage-regions-

Select your bucket and create a new folder, specific to your Veeam repository. I would always suggest to limit the object storage consumption. This way a misconfiguration doesn’t create excessive costs.

And, most importantly, don’t forget to configure the immutable time interval in days.

Next steps

For now, we can only copy existing backups to an object storage with scale-out repository and the capacity tier. So your finaly step will be, to create the scale-out repository and define how you want to upload/copy your backups to Wasabi.

In v12 this may change, as it’s planned to implement direct backup to object storage.

Hidden secret in v12

If you add an object-storage in v12, you might see a small change in the dialog. 😉

 


10 comments

Userlevel 7
Badge +8

Great post.  I use Wasabi and have it configured on my homelab in a SOBR.  Really great for just my small things I test and my upload to Wasabi is almost a full 1GB speed which is nice.  😎

I have seen new the new dialog as I am using v12 Beta2 for testing. 😁

Userlevel 7
Badge +8

Great article @regnor! I love that Wasabi is a first class citizen now in v12, nice to see something other than the hyperscalers being name dropped!

 

Appreciate you collating the support materials too for endpoint names etc, gonna be using Wasabi for my M365 backup (I don’t like the idea of backing up M365 to Azure personally), so I’ll be using this to speed through gathering that detail!

Userlevel 7
Badge +6

Hey @drews they are talking about you!

Userlevel 7
Badge +6

Great post.  I use Wasabi and have it configured on my homelab in a SOBR.  Really great for just my small things I test and my upload to Wasabi is almost a full 1GB speed which is nice.  😎

I have seen new the new dialog as I am using v12 Beta2 for testing. 😁

Their performance so far has been really more than ok. During a restore to Azure I’ve seen ~2Gbit/s in parallel.

@MicoolPaul In v12 you don’t event need to enter the URLs as they’re hardcoded; only the region needs to be entered. Storing the backups at a different provider makes sense; not only because of the different infrastructure but also the seperation of access/control.

Userlevel 7
Badge +8

Great post.  I use Wasabi and have it configured on my homelab in a SOBR.  Really great for just my small things I test and my upload to Wasabi is almost a full 1GB speed which is nice.  😎

I have seen new the new dialog as I am using v12 Beta2 for testing. 😁

Their performance so far has been really more than ok. During a restore to Azure I’ve seen ~2Gbit/s in parallel.

@MicoolPaul In v12 you don’t event need to enter the URLs as they’re hardcoded; only the region needs to be entered. Storing the backups at a different provider makes sense; not only because of the different infrastructure but also the seperation of access/control.

Wow 2GB very nice! 👍

Userlevel 7
Badge +3

Brilliant post @regnor Really simple and straightforward to implement. 

Userlevel 7
Badge +7

Very interesting and detailled post. Thank you @regnor 

Userlevel 1
Badge

Thank you @regnor for the kind words regarding your experience with Wasabi.
We’re stoked to make the short list of named parters in VBR v12!
If anyone is currently using the Wasabi free trial as part of an evaluation and needs more than 30 days, please send an email over to support@wasabi.com, tell them I sent you, and we’ll get you an extension!

Userlevel 7
Badge +3

Thank you @regnor for the kind words regarding your experience with Wasabi.
We’re stoked to make the short list of named parters in VBR v12!
If anyone is currently using the Wasabi free trial as part of an evaluation and needs more than 30 days, please send an email over to support@wasabi.com, tell them I sent you, and we’ll get you an extension!

Thank you!

Userlevel 7
Badge +6

Thank you @regnor for the kind words regarding your experience with Wasabi.
We’re stoked to make the short list of named parters in VBR v12!
If anyone is currently using the Wasabi free trial as part of an evaluation and needs more than 30 days, please send an email over to support@wasabi.com, tell them I sent you, and we’ll get you an extension!

That's great, thanks @drews! 👏 Especially if you're working with immutability for the first time, more than 30 days can be necessary or useful.

Comment