0% found this document useful (0 votes)
205 views

Tips & Tricks From Veeam Sizing

This document provides tips and best practices for sizing Veeam infrastructure components. It recommends 1 CPU core and 4GB of RAM per 10 concurrently running jobs for Veeam servers. For SQL databases, SQL Express can support up to 300-400 VMs, while a dedicated SQL server may be needed for more. Proxy servers should be sized to 30 VMs per CPU core as a starting point. Repository storage needs to account for compression and free space, and per-VM backups work best around 300 VMs per job. Resources for sizing tools and best practices documentation are also provided.

Uploaded by

Leon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
205 views

Tips & Tricks From Veeam Sizing

This document provides tips and best practices for sizing Veeam infrastructure components. It recommends 1 CPU core and 4GB of RAM per 10 concurrently running jobs for Veeam servers. For SQL databases, SQL Express can support up to 300-400 VMs, while a dedicated SQL server may be needed for more. Proxy servers should be sized to 30 VMs per CPU core as a starting point. Repository storage needs to account for compression and free space, and per-VM backups work best around 300 VMs per job. Resources for sizing tools and best practices documentation are also provided.

Uploaded by

Leon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Availability made easy for your Virtual

infrastructure: Tips & tricks from Veeam

Matt Crape Veeam Vanguard


Twitter: @MattThatITGuy
Mario Marquez – Sr Systems Engineer, Veeam Canada
Twitter: @veeamspeed
Veeam Sizing and Best Practices
Veeam Server Sizing Best Practices
• 1 CPU core (physical or virtual) and 4 GB RAM per 10 concurrently
running jobs.

• If Virtual 4vCPU Cores and 8GB RAM good for 300-400 VMs, and
backup/BCJ/Replication/Surebackup/Surereplica jobs included!!!

• Simple, just keep an eye on resources, ESX and Storage


resources…VeeamOne helps to let us know.

• Consideration

• SQL DB Express 300-400 VMs Max


Veeam SQL database sizing
• SQL Express 2014
• Each instance uses only up to 1 GB of RAM
• Each instance uses only up to 4 cores of the first CPU
• Database size cannot exceed 10 GB
• Up to 300-400 VMs is all good for backups/replication/BCJ etc.

• What about Staging servers?


• Explores SQL, Exchange, Oracle, SPS, AD, 10GB DBs?
• File to tape jobs
• SQL Versioning
• Dedicated SQL Server?
SQL Server Sizing cont.
:

Number of concurrently
CPU RAM
running jobs

Up to 25 2 4 GB

Up to 50 4 8 GB

Up to 100 8 16 GB

If possible follow these guidelines


Proxy Sizing Best Practices.
• Calculating Overall “Task” Count Examples
• Sample infrastructure has the following configuration:
• 480 VMs
• 48 TB used data
• Backup window: 8 hours Watch your Storage and Network
• Change rate: 5%
• For that, the following calculation can be used as a starting point.
• Using the "30 VMs per CPU core" rule, we get following result:
• +
• 480 VMs / 30 VMs per core = 16 CPU cores
• Each CPU core must have 2 GB RAM:
• 16 CPU cores x 2 GB RAM = 32 GB RAM.
• Result: 16 CPU cores and 32 GB RAM.
Repository Sizing and Flavors
• Server-Based Repository: DAS or SAN
• Windows or Linux?
• Physical or Virtual?
• Dedup Appliances ?

• Per Job = 1 CPU/Core + 4GB

• The more disks the better for safety and performance.


Repository Sizing cont.
• How much storage do we need?
• Be conservative
• Assume 2:1 Compression + 25% Free Sapce
• 10TB + 25% = 12.5TB
• VeeamOne has the numbers
• Sizing Tools http://rps.dewin.me/

• Per VM Backups
Sweet spot at around 300 VMs per backup job
• More available storage required, better synthetics performance
• Careful with BCJ, Health checks with large jobs

• SOBR Scale Out Backup Repository


• Less admin, Logical name, Per VM backups is a good option
Best Practices Resources
• Documentation
https://bp.veeam.expert/

• Sizing Tools
• Repository http://rps.dewin.me/
• VeeamOne Sizing http://one.mrferik.com/par.html
FREE STUFF
for Existing Customers
FREE Products
Veeam Agent for Linux:
FREE for 6 months

Veeam Agent for Microsoft


Windows: FREE for 6 months
(when available)

Veeam Backup for Microsoft


Office 365: FREE for 1 year
FREE Cloud Services
Get $1,000 in FREE
Cloud Services via
Veeam Cloud Connect
Free Stuff! All at Veeam.com

https://bp.veeam.expert for the full Veeam best practices


Q&A and Thank you
Visit Veeam.com!

You might also like