@Andanet You may want to check with HPE to see if they have any capabilities to help you out.  I misread the product you were using and thought it was an object storage platform that has a slightly similar name

I know on Linux you can remove the immutability flag with a command and then remove files but not sure if NetApp works the same way.  The new feature would have been great using the 12.1 but looks like you are contacting NetApp now to see.

When using S3 object locking apis, there are two retention modes:

1. Compliance
2. Governance

The details of these retention modes can be found here S3 Object Locking.

The major difference between these two is Compliance Mode doesn’t allow the removal or reduction of object lock retention once an object is written.  Governance allows that type of manipulation if they are given permission to do so.

Prior to 12.1 VBR only supported Compliance Mode, but due to the scenario of this topic we saw the need/use case to support Governance Mode in 12.1.

Thanks for sharing the details Steve.  Going to read up on this.  

Thanks @SteveF . I talking about HPE StoreOnce and probably is a question more focused on storage than Veeam. I hope anyone have some experiences. 

Thanks 

The key is for Amazon S3 and S3 compatible object storage only. Just in case @Andanet has asked specifically for StoreOnce immutability.

We don’t have such a key for DataDomain, StoreOnce and Azure repositories.

Best,

Fabian

This is also great to know Fabian as I did not realize it pertained specifically to Amazon only.

My apologies.  I read StoreOnce, but my mind processed StorageGrid.

I hate Monday mornings sometimes and this is one of them.

Would be great to see Governance mode supported on the DataDomain as well For the same reasons as any other immutable storage device.

I can tell you that if you’re using Wasabi object storage with immutability, if the client decides to leave, you’re stuck with the data until the flag expires.  There is not overriding that flag and removing the data administratively.  This includes deleting the bucket entirely, as you’ll get the below error message.

None of my clients have immutability beyond 90 days, but I did make the mistake of setting 1 year of immutability when I was testing things, which is why I can reproduce the below message when I try to delete the bucket with immutable data inside of it.  I know this isn’t entirely your situation, but just as a FYI with Wasabi storage, this is the case.

@Andanet Even with immutable objects you can delete a Catalyst Store. You'll just need to approve the deletion with a security officer account.

Thanks @regnor, as I wrote I appreciate very much you posts and from these I got inspired. Technically is correct the action to delete a Store. but now we must consider a lawyer aspect too. 

If a customer defaults and doesn't pay the invoice, is it legal to delete the data?

Thanks

Thanks for the kind words @Andanet 

The legal part unfortunately is out of my scope Probably this should be defined in the contract and approved by your legal department.