There is a time growth feature for you to set as well as your expected change rate so that will help answer your question. Make sure you check the refs/xfs box as this will give you the space savings effect you are seeing with multiple fulls. I would suggest setting it to backup copy job (I understand you are not doing a backup copy job in veeam, but this calculator does not seem to have the latest v10 changes where you can use gfs in a main backup job and so this gives you similar results and let's you configure gfs settings) One/some of their engineers created and maintain this I believe. But still only unique blocks are ever going to be sent to capacity tier.įor space figuring, you could try using this Eventually there are less similar blocks as the months and years go by so it may grow larger down the road. So your bucket is only going to grow similar to the size of your incremental backup sizes for a while. It is not dedupe but a way of preventing duplication in the first place. For ReFS based file systems the recommendation is to add 0.5GB RAM per TB of ReFS storage. For example: 7 cores 4 28GB RAM Always use 64 KB block allocation size. It works similar to the refs/xfs block cloning feature in those file systems. To calculate the required RAM, take the repository core-count and multiply with 4GB. Object storage in veeam is offloaded in incremental forever manner.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |