Thanks for the warning, but small note: SOSAPI is NOT required for immutability, SOSAPI extends the functionality and reporting of S3 further with Veeam:

In particular, the integration into the Veeam SOSAPI is missing, which means that Veeam cannot reliably read and control important information such as the capacity and status of the immutability.

https://helpcenter.veeam.com/docs/backup/vsphere/sosapi.html?ver=120

As we can see from the list SOSAPI is more of a “nice to have”, but not required for key features like immutability, and we have had immutability with S3 providers/servers for some time since before SOSAPI even existed ;)

SOSAPI would be a nice addition of course, but it’s not a requirement for immutability.

​@ddomask  I agree with you that SOSAPI is not a prerequisite for immutability.
This only came up in the ONTAP S3 constellation. Yes, I could have written more directly that this has nothing to do with each other, but would be a nice to have.

Since you have only touched on a subset of it, here is a link for more information: https://helpcenter.veeam.com/docs/backup/vsphere/sosapi.html?ver=120

​@PeteSteven: There is no connection between SOSAPI and Immutability. For anyone reading this, SOSAPI support is not a requirement for Immutability support with Veeam.

The post here is causing some confusion, and I hope folks coming here will see this comment or the one from ​@ddomask. 

​@haslund  I had already written this above and agreed that it is not necessary, but would be a nice addition. I don't understand why you have to go into it again here, as the comments already say.

I have modified the post and removed the SOAPI part completely. Hope it is more understandable now

Thank you for the update on the original post. As for why I replied, it was because both Veeam and NetApp received requests from customers confused by the original post (and where the readers did not read the comments). My hope was to get a change, and it appears to have worked.

For clarity, the article you are referring to https://www.veeam.com/sys539 does not list immutability as a feature and attribute. This is the same case for many other vendors. There is no reason to create a post here about each article, as the article could be updated with revised information at any given time if a vendor re-runs testing and passes the tests successfully.

As an example, the article was updated in May to reflect the following text: Warning: While ONTAP 9.14 and above support Object Immutability, this feature has never been tested successfully with Veeam Ready and currently does not function with Veeam Backup and Replication version 12.0 and higher.

However, that doesn't match with your screenshot in the article.

The text “no longer fulfills” is also misleading. It was never tested for Veeam Ready. I’m not sure exactly where you got this information, but it makes it sound like it was fulfilling the requirements and now does not, which is incorrect.

​@haslund 

I do not create a post for every article, but we were made aware that immutability was possible and tested and that this is no longer the case with ONTAP 9.14 and higher. I just wanted to point this out.

Ontap S3 with immutability was in the Veeam Ready program with Ontap 9.12.1.

​@PeteSteven: This is simply an untrue statement. I manage the Veeam Ready program globally, and NetApp never submitted any ONTAP tests to Veeam Ready where immutability was tested (successfully or not).

​@haslund  

ok, then I'm probably wrong here and can't find the old reports. From the comments below the post I understood that it was tested, but then this was wrong.

ONTAP 9.14.1 now supported with Veeam Data Platform 12.1. | Veeam Community Resource Hub

It will be best if the post is deleted and you also comment on the post in the R&D forum I linked above