I'm not R&D so I don't know these kind of internal details. I'm not saying this as a Veeam Employee or product manager. In order to make such an algorithm, choices had to be made: The new calculator uses this RPC code and thus have an internal split on a per file (it just doesn't show it for now). RPS would be more accurate but in the cases I have seen while testing it, giving it the exact same parameters, the calculation should vary maybe 5%. It just has a clever algorithm that calculates in one pass what the result should be but doesn't have to do the day to simulation. In order to make a more extensive SIZING tool, I've created a new library called RPC. There are a lot of people unaware that there is such thing as a manual mode. So 1 year ago we went back to the basic question, why are people using RPS? I can say that 95% of people are using it to do a sizing. However it also makes the code quite difficult to add functionality (as a single developer). This code is great because you can run manually scenario's and dig into the details. In fact if you give it 5 years retention, it will guesstimate when the worst case scenario would occur (in the next 6 years) and then runs through it day by day asking itself what VBR would do. RPS is quite extensive code because it simulates what VBR would do day by day. It's never been a full time job in fact it was more a hobby project for me. Let me reassure that I don't plan to take it down tomorrow but a lot of people have asked me over the years to keep it up to date and it is just not possible. Let me first say thank you guys because as the author of RPS I get a lot of positive feedback (even if it was me saying I'm deprecating the tool).

I'm not sure if I missed something but for now I'll stick to the old version. One (or both?) of the calculators is wrong.If I use the same values on both calculators, the result is totally different.įor example, I did a calculation with the follwing values: It was always useful to show to customers how a backup chain looked like with different settings. There are a few options missing like scheduled active full or synthetic full backups or estimated size of individual restore points. The official Backup Capacity Calculator ( ) is missing quite a few features compared to the unoffical Restore Point Simulator ( ).

Veeam vbo calculator