How does existing Wasabi customer start using S3 object lock?

[mfc]

Great news that Wasabi has finally released the S3 object lock functionality.

We're an existing customer of Wasabi and have been offloading backups to them via SOBR capacity tier. I know that object lock cannot be enabled on existing buckets, creating a new bucket and corresponding S3-compatible repository in Veeam is no problem. But I was reading the Wasabi integration guide and saw this note:

NOTE: To start using Veeam with Object Lock, you will need to create a new Performance Tier Repository(Local Repository), a new Object Storage Repository(S3-Compatible Repository), a new Scale-Out Backup Repository, and a new Backup Job or Backup Copy Job. You are unable to convert your existing Jobs to use Object Lock.

The Veeam recommendation for converting to Object Lock (Immutability) is to start a new Backup Job with Immutability enabled and phase out the old Backup Job.

For questions, please reach out to your Veeam support representative.


So if you have an existing SOBR and local (performance tier) repository, you need to abandon them and create new to start using object lock? As well as creating all new backup jobs?

Thanks

[Gostev]

No, not really. You can just change the object storage repository for the Capacity Tier. Our User Guide has this information > Migrating Data To Another Capacity Tier

[Mildur]

The first Option will let you migrate the bucket with the help from VBR Server itself. But the user guide from Gostev has a small error/missing description.

Migrating Data Between Different Cloud Providers

4. Copy or move your data to a new object storage repository, as described in Moving to Capacity Tier.

Step 4 is about copy or move the data from Performance Tier to Capacity Tier. The provided link in the guide only works for a „move“ operation.

If you want to copy the backups from performance tier to the new capacity tier, you can use this command for step 4.
post308683.html#p308683

Make sure, that you have configured Copy Policy for the capacity tier first and done already step 1-3.


————

You can also use the second option, if you have a third party S3 Migration tool.

[mfc]

Thanks for the response guys, that makes sense.

[chrisWasabi]

Hello All! I have updated the Wasabi Veeam Object Lock Integration Guide to a more appropriate response.

Cheers!

[Andreas Neufert]

Thanks @chrisWasabi and @dalbertson

[mfc]

One more question guys, as I understand it Veeam always uses Compliance Mode on backups to S3 when immutability is enabled. So it is not necessary to enable Compliance Mode on the Wasabi bucket itself?

[veremin]

Correct, you just need to enable the Object Lock and Versioning features on the bucket when you create it, and we take care of the rest. Thanks!