Why do I receive "Failed to disable backup immutability:S3 Versioning feature is enabled on selected bucket" with Veeam B&R?

Why do I receive "Failed to disable backup immutability: S3 Versioning feature is enabled on selected bucket" with Veeam B&R?

When configuring your Object Storage Repository based on Backup Job in Veeam v10 With Wasabi, you may encounter the error “Failed to disable backup immutability: S3 Versioning feature is enabled on selected bucket.”

Be aware that Veeam uses its own software algorithm and maintains a local DB for managing indexes. By definition, the Wasabi versioning feature creates multiple, versioned copies of objects. Veeam will only ever point to the current copy and it may not be possible to change the indexing to point to another object that is not the latest version.

With Wasabi versioning enabled for a bucket, the current files, as well as the older versioned copies, are kept. But, there is no way to utilize those from within Veeam, not even for restoration, since Veeam performs a restore using only the current objects that have been indexed.

There are two concerns with versioning enabled buckets on Veaam backup:

• Not breaking the Veeam chain in the local DB index.

• Growing the active storage volume in your account without actually being able to use those old versioned copies in Veeam.

Wasabi encourages customers who are using Veeam for their backups to disable the versioning feature.