The sizing information given in the user guide are minimums.For example if the server is both a Proxy and Tape server you will need to add the resource requirements for both together Sizing requirements are specific to each Veeam infrastructure component.Each disk that is backed up is a task this is not a per VM measure Some sizing requirements refer to “Per Task”.All sizing information is contained in the user guide and best practice guide.Some considerations when sizing your Veeam environment: Number of VMs and disks to be protected and number of retention points required will also be needed for disk capacity planning which I will cover in a future post.Can either be calculated assuming change rate as 10% of your total data size or from existing backup software Daily rate of change – This is required to understand the size of an incremental backup.
Size of source data – Required to calculate size of full backup.In order to plan your Veeam backup sizing you will need to gather some information The key components of the Veeam infrastructure you will have to consider in your sizing exercise are as follows:
During VeeamON I attended a session on Veeam sizing by Tim Smith, I have pulled together my notes from the session and reviewed the Veeam documentation to give the following template for considering Veeam sizing decisions. Correctly sizing the infrastructure to ensure that each of the Veeam infrastructure components servers has sufficient resources to perform its role will allow an optimally configured and trouble free environment. One of the key decision you have to make in planning a new Veeam deployment is in sizing the infrastructure.