Free Document

VeeamON 2022 – Industry Snapshot

VeeamON 2022

During the week of May 15, 2022, Veeam held its two-day VeeamON customer and partner conference in Las Vegas, Nevada – the first in-person VeeamON since 2019 due to the global COVID-19 pandemic. Through a series of presentations, product demonstrations, panel discussions and one-to-one briefings, Veeam leadership and staff provided insight into the company’s recent performance, strategic objectives, and its portfolio roadmap.

Takeaways from VeeamON

Veeam is no longer a single-solution company. Key growth metrics announced at VeeamON 2022 point to the company’s success in expanding from its core competency in protecting virtualized environments into protecting additional environments including infrastructure-as-a-service (IaaS), software-as-a-service (SaaS) and containerized Kubernetes environments. For example, Veeam reported 27% ARR growth year-to-year for its FY21, with growth to the flagship Veeam Availability Suite of 36% being outpaced by the Veeam Backup for Microsoft 365 business, which grew 73%.

Upcoming product updates announced at the show reflect Veeam’s evolution into a centralized solution for protecting physical, virtualized, containerized and cloud-hosted workloads.

  1. Veeam previewed Veeam Backup & Replication (VBR) Version 12, showcasing the addition of capabilities that accelerate cloud IaaS backup and recovery – specifically, application-consistent backups of cloud workloads as well as the ability to write directly to on-premises object storage targets, in addition to the off-premises object storage targets that were already supported.

Download now to continue reading this free Industry Snapshot report. 

Related to this document:
, VeeamON 2019 – Industry Snapshot, Data Protection Systems – Evaluation Guide

Related Research



Document Type:


May 25, 2022

Log-in or Register to ACCESS

This free document is available for registered users. Please log-in or create an account.

User Registration

Register for the site

This field is for validation purposes and should be left unchanged.