Veeam Adds 6 Hypervisors, Launches Cloud Archive Tier to Replace Tape
Veeam wants IT leaders to bet on one platform instead of five. Data Platform v13.1 adds six hypervisors, native protection that finally unites healthcare and non-x86 workload customers under Epic and Db2/Oracle, and a new archive tier built to replace tape. The real question is: Does putting recovery, security, and archiving under one vendor close the fragmented-visibility and standards-drift risk of running five separate tools, or does it just trade that for one giant backup target that’s easier for an attacker, or an admin, to break?
Four changes make up the v13.1 release
Veeam Data Platform v13.1 went generally available July 29 at VeeamON Sydney, alongside a new archive-class storage tier called Vault Archive. Four groups of changes make up the release:
- Hypervisor support: Expands from eight to 14 platforms. Six are new: Red Hat OpenShift Virtualization, Sangfor aSV, XCP-ng, Citrix XenServer, VergeIO, and Platform9. Five ship today; the OpenShift Virtualization plug-in arrives in the third quarter.
- Enterprise application protection: Native support for Epic’s electronic health record system and for Db2 on Windows and Oracle, with incremental merge for both, plus a general-purpose Application Backup Repository for custom applications.
- Threat detection: Malware scanning extended to network-attached storage, expanded cloud threat detection for Microsoft Azure, Active Directory Forest Recovery for faster identity restoration after an attack, cryptography aligned with post-quantum standards from the National Institute of Standards and Technology, and hybrid support for the Federal Information Processing Standards.
- Vault Archive: A new archival-class tier for redundant, obsolete, and trivial data. Immutable, encrypted, logically air-gapped, with customer-controlled key management and policy-based tiering out of the primary Vault. Pitched as a direct replacement for tape.
Consolidation closes the gaps between point tools
Veeam frames this release around cyber resilience. The more interesting story is cost and complexity: Every feature here removes a reason to run a second tool.
Backup and recovery has fragmented for a decade. Organizations run one tool for virtual machines, another for SaaS applications, a third for cold storage, and sometimes a fourth for ransomware detection alone. Veeam’s argument is that consolidating those functions into one platform closes the gaps between them, the handoffs where an attacker or an auditor finds the seam. Veeam frames this as a complement to endpoint detection and response, positioned downstream: If an attack slips past EDR/XDR, Veeam pinpoints when the data changed while EDR handles stopping the intrusion.
Veeam’s “Data Trust and Resilience Report 2026” found 90% of organizations were confident they could recover from a cyber incident, while fewer than 1 in 3 ransomware victims recovered all their data. That gap between confidence and outcome is the entire case for this release. Treat that number as a vendor-supplied claim rather than an audited fact.
Every feature removes a reason to run a second tool
Tool sprawl is the problem. Every feature here removes a reason to run a separate product. Application-specific protection closes a real operational gap for Epic and Db2 users. The hypervisor expansion answers the market Broadcom’s VMware price increases created. Vault Archive answers regulators’ demands for provable, location-aware data retention.
Four groups have different reasons to care
Healthcare IT leaders running Epic now get a backup path built for that specific system instead of a generic file-level copy. Financial services teams running Db2 or Oracle get the same treatment, with incremental merge reducing the backup window for large transactional databases.
A third group is anyone migrating off VMware. Broadcom’s pricing changes since its acquisition of VMware pushed customers to evaluate alternative hypervisors, and Veeam ties its hypervisor expansion to that pressure in its own release.
Teams already in the midst of migrating to Red Hat OpenShift Virtualization, Citrix XenServer, or Platform9 get one less integration to build themselves. Price competitiveness varies by platform: XCP-ng is free and open-source, while OpenShift Virtualization, Platform9, and Sangfor aSV are commercial subscriptions, typically priced well below Broadcom’s post-acquisition VMware licensing, but not free.
Compliance and data sovereignty teams should look at Vault Archive. Veeam’s research claims 58% of organizations rank data residency as the most important factor in where they store data. That is another vendor-supplied figure, but the pressure is real. Regulators are demanding provable, location-aware retention.
Vault Archive requires a governance decision first
None of this is automatic. Existing customers get v13.1 through their normal update path, but turning on Vault Archive’s tiering requires a governance decision first: what counts as redundant, obsolete, or trivial data, how long it sits before tiering, and where it’s allowed to live geographically. Veeam’s recent acquisition of Securiti AI is pitched as an answer to exactly that classification problem, using AI to automatically discover, tag, and risk-score data across the estate, but that integration ships separately from Vault Archive and isn’t live in this release.
Teams running Epic, Db2, or Oracle should confirm their database version and configuration against Veeam’s supported list before assuming coverage. Incremental merge changes backup windows for large databases, and that changes existing service level agreements with the business units those databases support.
Anyone building a hypervisor migration timeline should treat the Red Hat OpenShift Virtualization plug-in as a third-quarter deliverable. It hasn’t shipped in July. Committing to a cutover date on the assumption that support ships today is a mistake.
Veeam’s hypervisor lead won’t last, but Vault Archive might
Veeam’s differentiator is breadth inside a single management plane. Rubrik, Cohesity, and Commvault are each making similar consolidation arguments, but Veeam’s hypervisor count, now 14 with more promised through its Universal Hypervisor API, is the widest in the category.
Breadth alone isn’t a moat.
If a competitor matches the hypervisor list next quarter, this advantage disappears. The tape-replacement pitch behind Vault Archive is a sharper differentiator. It sells operational simplicity: no tape libraries, no manual handling. Cheaper storage isn’t the pitch. Tape’s raw cost per terabyte in a climate-controlled facility can still beat cloud archive pricing at multipetabyte scale over a multiyear retention window, and Veeam hasn’t published numbers that settle the comparison. Cloud-native, immutable archive tiers built into a backup platform’s own workflow are rare enough that most enterprises still run a hybrid of cloud backup and physical tape for their coldest data. Veeam is asking customers to trust one vendor for both the hot recovery path and the cold compliance path. That concentrates risk with the vendor while it reduces vendor count for the customer.
Our Take
Combining these tools only pays off if the combined platform gets data back faster than the separate tools it replaces. Platform consolidation is a pitch vendors make constantly; internal architecture, and often internal politics, usually slows execution more than the technology does. Veeam’s own numbers show a gap between how confident companies feel and how much data they recover. Closing that gap is the real test. Backup is solved; recovery isn’t.
The built-in support for Epic and Db2 is the most useful part of this release. It fixes a real gap instead of matching what competitors already offer. The added hypervisor support responds directly to the market Broadcom’s VMware price hikes created, giving migrating customers a practical option.
For most CIOs the answer is qualified: Consolidation lowers the operational risk of running five uncoordinated tools, but it raises the concentration risk of handing one vendor recovery, security, and archive at once. Which risk your organization is better equipped to manage should decide the call.