StoreOnce 3460 – Backup Immutability Not Working as Expected

[carlostorres]

We are facing unexpected behavior when configuring the immutability feature between HPE StoreOnce 3460 and Veeam Backup & Replication 12.1 (build 12.1.1.139), using a Catalyst repository.

 Symptom:

Even with immutability enabled on the StoreOnce side, it is possible to manually delete backup files from Veeam, as long as those backups were not marked as immutable within Veeam.

Question:

According to HPE StoreOnce documentation, enabling server-controlled immutability should apply minimum retention enforcement and prevent deletion regardless of what the ISV (Veeam) specifies.

However, the current behavior is:

If the backup is not marked as immutable in Veeam, StoreOnce allows deletion, even though server-controlled immutability is enabled.

If the backup is marked as immutable in Veeam, StoreOnce correctly blocks deletion.

[Cali · Accepted solution]

Hi,

for Veeam, always set "Maximum ISV Controlled Data Retention" on Store Once to maximum (365000).

On the Catalyst Store DO NOT ENABLE the “Server Managed Immutability” because it is not supported.

See: Data protection with Veeam Backup & Replication, HPE StoreOnce, and HPE StoreEver Technical white paper

Also:

HPE StoreOnce Supported Features - User Guide for VMware vSphere

HPE StoreOnce - User Guide for VMware vSphere

Cali

[carlostorres]

Thank you for your response. I’ve read the recommendation provided by Veeam; however, I couldn’t find any HPE documentation that makes a similar reference.

[Cali]

I know that; you have to know exactly where to look.
I find this guide the best: Data protection with Veeam Backup & Replication, HPE StoreOnce, and HPE StoreEver 

Cali