Hello is there any plans to integrate this with VBR more, example it would be great to load Backup metadata into it to pull actual real life compression and dedupe numbers as well as more accurate incremental numbers. It seems you can never get the VBk or VIB to show really anywhere close to what you have for existing backups and I understand you want to over-allocate but this seems to do it way too much. Being able to load let's say a week's works of backups where you could have a solid avg size of Vibs and actual VBK size on disk then can really calculate what your different storage needs would be for any retention instead of manually calculating after using the tool.

Capacity/size labels are showing in Base 10 (GB/TB). However, the input fields and math appear to be using Base 2 (GiB/TiB), which means the labels are incorrect. At larger capacities, the discrepancy between TB and TiB can be substantial. I would suggest changing the labels on the page and/or adding a note indicating the differences.

Hi, first of all thanks for this resource, it's been very helpful.
I was wondering which function is used to calculate "workspace"? I'm trying to understand how it decreases as the data from origin grows.
Thanks

Hello,
thank you for this tool. with the new v11 could you add the immutability retention support ? ;)
thank you.

First of all, love the tool, I appreciate your time a lot!

I would just like to understand how 'Backup Chain Transform' would affect the storage requirements, as from my understanding, it doesn't need to keep the initial Full Backup as with using Synthetic Full's alone.

PS, the manual run option really helped me understand Veeam behaviour better than any document! - Thanks again!

How do I convert the results to Excel or PDF or any external file? I tried an Export option - I got a link that takes me back to the same table.

I have many servers that i am looking to calculate backup copy jobs for and would like to upload multiple server storage with the same retention and then calculate what each total would be. If able to port to an excel macro would be beneficial.

So I'm trying to figure out how to properly calculate cloud connect. Obviously it's a copy job but what I'd like to is add a weekly synthetic full. Not sure how to do that in the calculator. say I have 10TB with 10% Change Rate adn 50% compression. I would assume it would be initial full of 5 TB with dailies of 500GB. I would assume my max storage would be 2x 5TB(initial full plus weekly) plus 6 X 500GB= 13TB but calculator shoes 15500. Any thoughts?

Hi,

What license is this code released under?

Hello!

I am looking for clarification (or perhaps error correction) in a specific scenario I've run into.

Running a calculation using the RPS in a scenario with the following parameters:

Incremental Backup
10TB
14 restore points
all else defaults
All 12 months selected for Active Full

(http://rps.dewin.me/?m=1&s=10000&r=14&c=50&d=10&i=D&dgr=10&dgy=1&dg=0&im=1,1,1,1,1,1,1,1,1,1,1,1&e)

Such a configuration results in a seemingly strange calculation in regards to restore point retention where the total retention is 48 points and the number of VIBs from first VBK to second is 35. Removing a month and re-running the calculation results in a marginal increase of points as well.

I'm trying to wrap my head around whether or not these monthly active full backups act in the same way as weekly active/synth fulls do and modify the chain, but even then the math doesn't seem to add up in my head.

If this is indeed working as intended, would you mind explaining how the math works out?

Thanks!

As outlined here: https://www.veeam.com/blog/v11-gfs-retention.html Veeam have made a disruptive change to the way archive backups are processed. Specifically not doing forever incremental anymore where the regular .VBK rolls up the the oldest .VIB once the restore points were reached (only with GFS switched on).

Does this mean there needs to be a change to the calc for backup copies (with v11+/GFS only)?

We missed this in the update notes and found out once our 2-restore point jobs with 1 monthly/yearly archives jumped from 4-5 restore points to 37, because it had to keep a whole month of incrementals between the monthly .VBKs after the upgrade. The easy fix is just to add in at least 1 weekly archive (or not use GFS) to cut down the chain lengths.

Hi,
Do you have any plans to include dedupe ratio?
I have a case where full backup in the incremental is taken with dedupe 2,5x while rest of incrementals is about 1,0x dedupe.

Hi! Nice tool for calc Veeam Repos.

As a new feature i will suggest export as Excel, easy done with datatables scritps!

Regards

Do you have any plans ( assuming it’s feasible) to setup the necessary calculations to estimate what effect the ReFS space savings may have on overall storage utilization?

Sorry if this suggestion sounds rude (especially on Christmas Eve), but I think the "Configuration" interface needs to revamped to match the interface as to how we see it when editing a Backup Copy job in Veeam.

There are just too many questions/choices that it's hard to tell if what we put in on the website matched EXACTLY the settings in Veeam.

OR, if that's too hard (hopefully it's not just me), at least some popup screenshots showing exactly which value a particular field is asking.

Thanks for the considerations.

Merry Christmas, y'all!

Hi any chance you would consider updating the interval section to allow simulation of either weekly or monthly backup intervals?

Hi Timo,

it seems that when you activate the Time Growth Simulation in Backup Copy Job Style
the yearly retention doesn't work anymore. Needs to be fixed.

There seems to be a bug in the working space calculation.
Calculation seems ok on first 2 tests but when numbers get bigger it fails to return a proper result.
See results table attached.
calculator test.pdf

Any plans on adding Capacity/Cloud tier sizing to this?