Veeam VBR (v11)

What is VBR?
"Veeam® Backup & Replication™ (VBR) delivers Availability for ALL your cloud, virtual and physical workloads. Through a simple-by-design management console, you can easily achieve fast, flexible and reliable backup, recovery and replication for all your applications and data."


Veeam...

  1. Veeam is agentless

  2. Built-in advanced replication

  3. Instant VM Recovery

  4. Instant File-Level Recovery

  5. Instant application-item recovery

  6. Automated recovery verification

  7. Built-in, source-side compression and deduplication

  8. Simple offsite backup

  9. Storage agnostic

  10. Easy to deploy and configure


Veeam Cookbook for Veeam Backup & Replication

Veeam Architects Site


Dive into VBR with a guided hands‑on lab experience. - Within 15 minutes, you will get a confirmation that your lab is ready. Once you submit your promo code you will have 3 hours to use the lab before it expires.

Basic Veeam sizing questions...

  1. How much source data (in TB)?

  2. How many VMs/Servers need to be protected? (Optional: Number of disks?)

  3. What is the backup window (in hours)?

  4. What is the daily change rate in percentage? (5% optimistic-9% conservative)

  5. What is the required retention schedule? (Optional: What are your RPO and RTO values?)

"Veeam VBR 11 Editions Comparison.pdf" (Click Here)

Please contact me for the "Veeam VBR 11 Editions Comparison.pdf" document.

Veeam Universal License (VUL) along with a Socket License
If you still use a socket license, we recommend you talk to your sales representative about migrating it to VUL for the ultimate capability and flexibility. However, if you must continue using sockets, please be aware of the following limitations:

  • When combining VUL with a legacy socket-based license in a merged and centrally managed environment, the socket edition and support level always takes precedence and dictates the feature edition level of the entire environment.

    • Example: Combing a Standard legacy socket license with VUL will restrict certain platform capabilities like the Scale-out Backup Repository.

  • If a feature isn’t available with a socket license, like cloud machine protection for example, it will be available when a VUL is merged with socket licenses.

  • In the presence of a socket license, all VMware vSphere and Microsoft Hyper-V VMs will consume the socket license. In other words, you cannot use VUL to protect some of your VMs unless you migrate the socket licenses to VUL, which can freely protect all workloads regardless of hypervisor, workload or environment.

  • VMs on hypervisor hosts that are licensed with a socket license can now be protected with any Veeam product without needing an additional VUL license, so long as the protection is managed by the same backup server. For example, protecting a Windows failover cluster based on vSphere VMs with Veeam Agent for Microsoft Windows does not additionally consume a VUL license for the agent."

Click here for more information on VBR

"Veeam Backup & Replication Community Edition is the must-have FREE backup software for VMware and Hyper-V, as well as physical servers, workstations, laptops and cloud instances. Use Community Edition to protect VMs, cloud instances, physical servers, workstations, laptops or unstructured file data. Protect your production environment, your remote worker endpoint devices, use it in your home lab or even for migrations at no cost — it’s like a FREE gift from Veeam!" (How to setup Veeam to manage all the backups in your home)


Non-Technical Information...


Veeam Backup Server Best Practices
Recommended Veeam backup server configuration is 1 CPU core (physical or virtual) and 4 GB RAM per 10 concurrently running jobs. Concurrent jobs include any running backup or replication jobs as well as any job with a continuous schedule such as backup copy jobs and tape jobs. The minimum recommendation is 2 CPU cores and 8 GB RAM.

Max number of *concurrent* jobs

  • 1 CPU core for every 10 actively running jobs at its busiest.

Max number of *concurrent* jobs

  • 512 MB for every actively running job at its busiest.

Space usage

  • Logs: 3 GB for every 100 VMs that back up once per day.

  • Working space for indexing: 100 MB /1 million files on Windows, 50 MB / 1 million files on Linux.

  • Indexing post-processing: 2 MB / 1 million files (compressed)

Laws of physics...
How long will it take to transfer 10 TB of data over a 10 Gbps link?

  • 10 TB = 10 * 1,024 (GB) * 1,024 (MB) = 10,485,760 MB

  • 10,485,760 MB / 900 MB/s = 11,651 seconds - (Note: 10Gb/s Ethernet is 1250MB/s theoretical, or 900 MB/s field experience.)

  • 11,651 seconds / 60 seconds in a minute = 195 minutes

  • 195 minutes / 60 minutes in an hour = ~3 hours 15 minutes


Technical Design and Architecture...

Technical Details...

Virtual Lab / DataLabs...

Agents...

Application Awareness...

Cloud...


Global Cache on Spinning Disk

  • Link <3Mb/s - WAN likely saturated; processing rate dependent on data reduction ratio (estimated 10x)

  • Link >3Mb/s and <50Mb/s - WAN will not be fully utilized; expect ~5MB/s processing rate but less bandwidth

  • Link >50Mb/s - WAN will not be fully utilized, using direct mode copy will use more bandwidth but likely be faster


Logs: C:\ProgramData\Veeam\Backup\Utils\VMC.log


Cryptographic Module Validation Program CMVP