![]() 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. It works similar to the refs/xfs block cloning feature in those file systems. This includes support for virtual workloads, physical workloads, enterprise applications and unstructured data. ![]() Object storage in veeam is offloaded in incremental forever manner. You can store backups of your on-premises workloads on Azure Blob using Veeam Backup & Replication, allowing you to use Azure Storage's pay-per-use model to easily scale your backup infrastructure with durable, cost-effective storage.
0 Comments
Leave a Reply. |