The total number of objects amounts to 3,410 objects as per table below: Use case: Organization with 500 users might need to protect all mailboxes (Primary and Archive) 200 Shared Mailboxes, 10 Public MailFolders, all Personal Sites and OneDrives along with 1000 SharePoint sites and 100 Teams. Sites (Collaboration, Communication, Publishing, Enterprise, Template based) including subsitesįor OneDrive for Business Online and On-Premises.The following list shows what counts as an object for Veeam Backup for Microsoft 365: Sizing the VB365 compute infrastructure is based on the amount of objects which need to be processed in the backup. The sizer uses the principles of this best practice guide to calculate storage and compute sizing. Make use of the official Veeam Backup for Microsoft 365 calculator at. Veeam Backup for Microsoft 365 calculator Use the official Veeam Backup for Microsoft 365 calculator.I hope you like this script and if you have any questions please leave a comment. StorageNeededinGB = ( $JobMath2 + $JobSize ) - $FreeSpace $DestinationStorage += $Details EstimatedRequiredSpaceinGB = $JobMath2 + $JobSize $Details. EstimatedFullBackupSizeinGB = $FullBackupSize $Details. TotalCapacityinGB = $TotalCapacity $Details. First we start to make sure the Veeam Powershell snapin is loaded: if (( Get-PSSnapin -Name VeeamPSSnapIn -ErrorAction Silentl圜ontinue ) -eq $null ) " -f $avgdiskchanges / 100 * $JobSize ))
It’s time to start a script editor to write some Powershell code. So now we know the formula, the next step will be to find the data to fill the parameters to calculate the disk space requirements. So make sure to visit it once in a while. There is a lot of good information there. This formula comes from the Veeam Communities. R = number of rollbacks (or increments) according to retention policy (14 by default)ĭ = average amount of VM disk changes between cycles in percent (we use 10% right now, but will change it to 5% in v5 based on feedback… reportedly for most VMs it is just 1-2%, but active Exchange and SQL can be up to 10-20% due to transaction logs activity – so 5% seems to be good average) This is the formula:ĭata = sum of processed VMs size (actually used, not provisioned)Ĭ = average compression/dedupe ratio (depends on too many factors, compression and dedupe can be very high, but we use 50% – worst case)į = number of full backups in retention policy (1, unless backup mode with periodic fulls is used) Before you can calculate these values you need to know the formula which Veeam uses to calculate the storage needs. You can use the Check Space button to verify if there is enough space to write the backup to disk:īut is it possible to get this values via Powershell. When you edit or create a new backup job in Veeam Backup and Replication. This post is about how to calculate the storage needs for the configured Veeam Backup Jobs.
0 kommentar(er)
