Hi,
what is the impact of immutability on regarding required capacity in a physical s3 storage solution ?
For example a 30 day backup with syn full on sat.
- full - 1000 GB
- incr - 100 GB
Having a object lock for 90 days, is it ok to say that we need to consider 60 x 100 GB ( incremental backup size ) for additional storage overhead in the S3 storage ?
any help with the real math would be appreciated
-
- Service Provider
- Posts: 453
- Liked: 30 times
- Joined: Dec 28, 2014 11:48 am
- Location: The Netherlands
- Contact:
-
- Veeam Software
- Posts: 291
- Liked: 139 times
- Joined: Jul 24, 2018 8:38 pm
- Full Name: Stephen Firmes
- Contact:
Re: Impact immutability on s3 storage capacity
@lowlander when VBR offloads data to the capacity tier, we use a block cloning methodology similar to ReFS to only copy/move unique objects to the S3 target. When you enable immutability we lock the objects for the period of time you configure on the object storage repository. If a locked object is referenced by a newer backup chain, we will extend the object lock for 10 days via our block generation process for any referenced objects. Since these extended referenced objects are "replacements" for the new duplicate objects, the net gain is negligible. You can use this restore point simulator https://rps.dewin.me/ by selecting ReFS/XFS.
Thanks
Steve
Thanks
Steve
Steve Firmes | Senior Solutions Architect, Product Management - Alliances @ Veeam Software
Who is online
Users browsing this forum: No registered users and 5 guests