In the Vault calculator, I noticed that it allows setting a retention period shorter than 30 days. However, according to the documentation, Azure Blob Cool storage as well as Vault has a minimum retention requirement of 30 days, and deleting data earlier could lead to additional costs or non-compliance. Shouldn't the calculator enforce a minimum of 30 days to reflect this constraint, or is there a specific reason why it allows values below that threshold?
Question
Vault Calculator Retention
Thanks
However, VBR allows the configuration of < 30 days, thus we changed the Calculator to match.
Consider that minimum vault retention does not necessarily imply minimum immutability, nor does it imply minimum backup retention/restore points. I’d prefer to think of it more like a minimum “stay” or minimum “storage time”. What it comes down to is that any backup blocks (objects) written will stay there a minimum of 30 days no matter what mix of immutability and backup retention is used to manage the lifecycle of those blocks.
E.g. 1 day immu + [10 day block generation] + 7 days backup retention = 18 days
- Is valid configuration, but doesn’t satisfy 30 days minimum stay.
- Data in the vault will be stored for 30 days, even after “deletion”/expiration from within VBR after the 7 day retention.
- In this config, you may as well increase one or the other (or both) settings since you’re measured on it anyway.
E.g. 14 day immu + [10 day block generation] + 7 days backup retention = 31 days
- Is valid configuration, AND satisfies 30 days minimum stay.
- Data will be stored for the full 31 days, and deleted data will actually delete thereafter.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.