Feature Request- Set Immutable Period for a backup set ad-hoc

[Skyview]

Scenario:
We're an MSP for healthcare institutions (Radiology). We backup Radiology data, which in most cases never changes and never gets deleted. Great use case for cloud object storage, especially with immutability. We backup via reading file shares. The data is split into chunks locally (DATA1 volume is written to until it fills up, then DATA2, etc etc)

However, we can only set immutability on our backup sets to 90 days. So while a customer may have decades+ of data, only the last 90 days worth is immune to ransomware.

As old backup sources are filled up, never to be backed up again, we simply unschedule or disable the job. However, we can't keep that backup data in object storage immutable. At most, it's only immutable for 90 days since the last backup.


In other words, companies may have a data source that while they don't need to keep it backed up regularly, they need to keep it immutable for compliance or other reasons.

It would be great if we could go to the backup set under Backups->Object Storage->(Backup Job Name), and right click into a menu where we could set the immutability end date. Veeam is aware of every object's location, and to set immutability it's just a single API call per object. Veeam knows how to do that already.

As an MSP, our customers renew with us every 3 or 5 years. I could set the immutability end date to 1 month after contract expiration. If they renew, I go in 1 month after they renew and set the date out another 3 or 5 years.

Would be a great feature to have. Yes, I know we can script this on our own, but it's messy.

[oleg.feoktistov]

Hi,

However, we can only set immutability on our backup sets to 90 days. So while a customer may have decades+ of data, only the last 90 days worth is immune to ransomware.

This limitation is in the UI only. In Powershell or REST the immutability period limit for hot/in-frequent storage classes is 999 days. With GFS backups you can have 999 years of immutability on SOBR Archive Tier.

Let me know if it helps with your use case.

It would be great if we could go to the backup set under Backups->Object Storage->(Backup Job Name), and right click into a menu where we could set the immutability end date.

I will need to check it with QA. We have a cmdlet that does that, but it works only with backups on linux hardened repos.

Best regards,
Oleg

[Skyview]

Thank you Oleg.

The helpful feature here is to be able to define and set immutability for rolling periods of time. Due to either compliance or contract status, it would be great to be able to go to a backup set, and ad hoc set immutability for that backup set for a defined period.

Let's say I have a backup set that is no longer receiving backups, but we have to keep it around. Maybe not forever, but for the next 3 years at least. I could go to that backup set, right click->Set Immutability, and define a date 3 years out. Veeam then flips that on for every object in the backup set.

3 years later, immutability expires. Nope, still have to keep it around for another 2 years. Right click->Set Immutability, and define a date 2 years out. So on, so forth.

[oleg.feoktistov]

Checked with QA. At the moment we don't have any interface or tool for the case you are describing unless it's about linux hardened repositories. So, noted it as a feature request. Thanks!