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!
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!
Statistics: Posted by patbcf — Apr 22, 2025 9:34 am