Immutable SAN Repository

[mamosorre84]

Hi,

is it possible to use a storage device with WORM feature as immutable primary repository instead of the v11 linux repository with immutability?

If not, what are the main reasons?

We are planning to buy a Huawei OceanStor 2600 v5 with HyperLock (WORM) feature, and we would like to know if it is possible to use the native functionality.

Thanks

Marco S.

[Andreas Neufert]

Remember we are overwriting data and need to be able to delete backups when we want. If you can not delete backups (WORM), we will treat the chain as damaged (something wrong with the storage) and do not continue backups.

The only way we are compatible with storage immutability is, to use something like a delete basket (Exagrid) or Immutable Snapshot (Pure Storage) that allow us to maintain everything in our chain, while the backup files are protected in the background.

[mamosorre84]

Hi Andreas,

I understand the problem about deleting/overwriting restore points.

But if we use periodic full backups, can't we avoid these problems?

Example:

- daily backup job with a weekly full and 8 days retention
- WORM set to 7 days

Shouldn't it work that way?

Thank you

Marco S.

[Andreas Neufert]

No, it will not change anything. The chain would be marked in repair stage when we can not delete data and you can not continue with the backup (only creating another active full and later manually deleting data).
As I shared look into snapshot immutability which is possible there. If I remember right Huawei has an option to create linke volumes and can mark them immutable. But you need to discuss this with Huawei.

[mamosorre84]

Sorry Andreas but I don't understand why you say you cannot delete data in the chain..

In my example you have 7 days for WORM, and if I'm not wrong, with 8 restore points you are going to delete the first chain on the 15th day, when all first 7 restore points are not locked anymore..

Isn't it?

[Andreas Neufert]

No, whenever we want to delete something and can't the chain is broken.
As well we have files like the metadata files that we overwrite all the time.

It is not supported and is not working reliably.

[mamosorre84]

Regarding metadata files, it is possible to set WORM exclusions for specific extensions/regex pattern..

I agree it is not supported and is not working reliably, but it is technically possible in my opinion!

[Gostev]

Technically it will work until it does not (when you run into some corner case that requires modifying/deleting a backup file).
But if you're fine about using something that is "not supported and is not working reliably" then we can't really stop you

[Andreas Neufert]

Please check with a Huawei Solution Architect your options.
If I understand it correctly, the WORK filesystem is exported to Veeam by SMB (or NFS).
In theory you should be able to create a new linked volume out of the underlying volume and mark this immutable (like a snapshot that is immutable).
Please check with the Huawei Solution Architect if this is possible in that way.

[mamosorre84]

Technically it will work until it does not (when you run into some corner case that requires modifying/deleting a backup file).
But if you're fine about using something that is "not supported and is not working reliably" then we can't really stop you

I'm not fine, I understand the risk..we have to stop my boss!