High object storage consumption due to daily changes

[patbcf]

Hi,

We have a customer in the construction industry who deals with a lot of daily changes. Since we backup data (snapshot) every day, all these changes keep filling up the storage. Maybe a third of the data actually needs to be kept for longer, after the cleanup was done by the users some days later. But all the changes stay in the repository according to the retention policy.

We're now looking into ways to configure our backup jobs and repositories in the most storage-efficient way. We’ve noticed that the current scheduling and retention policy settings give us very little room to adjust things — for example, keeping 7 or 14 daily backups, plus weekly or even monthly backups for longer retention periods of 5 or even 10 years.

What options do we have, and what has your experience been with high daily change rates and their impact on storage usage?
I really appreciate any insights, tips, or suggestions you have on what we could do differently.

cheers!

[edh]

Hi,

You can create multiple repositories with diferent retentions and multiple task, maybe in your case will be usefull a 7d, 30d, 1yr, 5yr , unlimited and adjust storage purge to 7d,30d etc...

But each repository will need a task for download the data with its own cleaning task.

In any case your data will be x5 of the original hosted in the customer. We got a customer that every day create 1 TB of new data, 350-370TB yearly.

Host this kind of data is not cheap, because veeam office 365 need a speedy storage for manage changes , resyncs and deletes. Also inmutability add some storage complexity depeding your backend.

Also VBO create billions of objects per tenants due the data nature of the service.