This episode reviews Veeam's history from its founding in 2006, the Availability philosophy (backup + replication + failover), to the Broadcom acquisition in 2025 and the v13 release (November 2025) that marked the Veeam Data Platform era. You will also understand why Veeam is needed: multi-hypervisor, Instant Recovery, SureBackup, ransomware protection, and Kasten integration.

Now that our environment is ready from episode 0, it's time to understand why Veeam exists. Every great technology is born from a real problem, and Veeam is no exception. In episode 1 we trace its history from the founding in 2006, the evolution of its philosophy into Availability, the acquisition by Broadcom in 2025, up to the v13 release (November 2025) that marked the era of the Veeam Data Platform.
The question we will answer: what makes Veeam different from other backup tools? Why do enterprise companies choose it to protect VMware, Hyper-V, Proxmox, and even SaaS? These answers matter because they determine when you should choose Veeam in production.
Veeam was founded in 2006 by Ratmir Timashev and Andrei Baronov. The name "Veeam" comes from VE (Virtual Environment) + AM (Availability Management) — from the very beginning, the focus was not just backup but availability. Starting as VMware management tools (FastSCP, Reporter, Configurator), Veeam then launched Veeam Backup & Replication in 2010 and became the de facto standard for VMware backup.
Its philosophy is clear: Availability. Backup is only half the story; the other half is the ability to replicate and fail over to restore services as quickly as possible when a disaster occurs. The concepts of RPO (Recovery Point Objective) and RTO (Recovery Time Objective) are the everyday language of Veeam design — we cover them in detail in episodes 7 and 9.
In 2025, Veeam was acquired by Broadcom — the company that also absorbed VMware. This move raised concerns among many admins (given VMware's licensing changes), but Broadcom's strategy actually strengthened Veeam's position as a cross-hypervisor data protection platform. What matters for you: Veeam continues to support VMware, Hyper-V, and now Proxmox equally — there is no vendor lock-in. We discuss the implications in episodes 17 and 21.
The Veeam Data Platform v13 release (build v13.0.0.3763, November 2025) marked a product name change: Veeam Backup & Replication is now part of the Veeam Data Platform, a single umbrella that unites B&R, Veeam ONE, Veeam Backup for M365, Kasten by Veeam, and Veeam Backup for Salesforce. Key v13 features:
One tool for all data sources: VMware, Hyper-V, Proxmox VE, Nutanix AHV, physical servers (via Veeam Agent), cloud VMs, Microsoft 365, Salesforce, and Kubernetes (via Kasten K10). This eliminates the need for many different backup products — one console, one policy.
Two features that set Veeam apart from "ordinary backup" tools:
Layered defense against the greatest modern threat: immutable repositories (S3 object lock / hardened Linux repo), Veeam CyberDCR (Ransomware Detection, Malware Detection, Cleanroom Recovery), AI anomaly detection, and network segmentation. We break this down thoroughly in episode 13.
M365 backup (Exchange Online, SharePoint, OneDrive, Teams), Salesforce, and Kubernetes via Kasten K10 make Veeam the most complete platform — one vendor for data center, cloud, and SaaS. This is relevant because many organizations assume SaaS is "already backed up by the provider" — when in fact the provider only guarantees availability, not your data loss.
Important
Microsoft 365 is not automatically backed up. The Microsoft SLA guarantees service availability, not recovery of deleted data, ransomware, or compromised accounts. The same rule applies to other SaaS — this is why Veeam Backup for Microsoft 365 is so popular (episode 11).
To position Veeam, remember the four main currents:
We compare them thoroughly in episode 22 — including when Veeam is not the best choice.
Key takeaways:
In the next episode, episode 2, we will dissect Veeam's core concepts and main architecture — how the Veeam Backup Server connects to Backup Proxies, Repositories, and other infrastructure components, including transport modes (SAN/NBD/HotAdd) and the role of the WAN Accelerator and Enterprise Manager. This is the anatomy that will explain every configuration in the episodes that follow.