VBR: Immutable object storage with Wasabi


Userlevel 7
Badge +14

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. 😉

 


31 comments

Hi All,

I’m wondering if anyone has replicated data from a standard Wasabi bucket to a immutable Wasabi bucket and changed over the scale out repo in Veeam?

If this has been tried has there been any issues?

Userlevel 7
Badge +20

Hi All,

I’m wondering if anyone has replicated data from a standard Wasabi bucket to a immutable Wasabi bucket and changed over the scale out repo in Veeam?

If this has been tried has there been any issues?

Never tried this but if you do and it works let us know.  Might be an easy way to move data.

Hi All,

I’m wondering if anyone has replicated data from a standard Wasabi bucket to a immutable Wasabi bucket and changed over the scale out repo in Veeam?

If this has been tried has there been any issues?

Never tried this but if you do and it works let us know.  Might be an easy way to move data.

It would be using the Wasabi bucket replication, then rescanning the bucket in Veeam - just curious how Veeam would handle the data when the bucket is sync’d and if it would match up the recovery points.

Wasabi Bucket Replication - Wasabi 

Just one question, if we need more than 30 day of immutability… like 365 day how can you setup this ? What is the best practice to do that ? Thx in advanced for you answers ;)

Userlevel 7
Badge +20

Just one question, if we need more than 30 day of immutability… like 365 day how can you setup this ? What is the best practice to do that ? Thx in advanced for you answers ;)

If you are using Wasabi that is set within Veeam versus Wasabi.  You just need to enable Immutability on the bucket in Wasabi, then set your retention settings in Veeam to what you need.

Userlevel 7
Badge +14

@GregCloke From a technical perspective it will be interesting to see if this works.

From Veeam's perspective this will be unsupported. Veeam suggests to start with a new bucket and either create new backup chains or copy the existing backups from within Veeam. Everything else could lead to unpredictable issues. If you really need to go this way, I would contact support before and see if there's a supported way if achieving this.

Comment