When configuring your Object Storage Repository based on this guide, you may encounter this 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. The Wasabi Versioning feature by definition creates multiple versioned copies of objects but Veeam will only ever point to the "current" copy and it may not be possible to change the indexing to point to any other object which is not the latest (current version).
So with (Wasabi) versioning enabled for a bucket, the current files are kept as well as the older versioned copies, but there is no way to utilize those from within Veeam, not even for restoration since Veeam performs a restore only using the "current" objects which have been indexed.
With that in mind there are two concerns with versioning enabled buckets on Veaam backup:
1. Not breaking the Veeam chain in the local DB index
2. Growing the active storage volume in your account without actually being able to use those old versioned copies in Veeam.
For this reason, currently we encourage customers who are using Veeam for their backups to disable the versioning feature.