Products

Closing the Data Protection Gap in the Post-VMware Era with Arcfra Data Protection Adapter

Published on 2026-09-15 by Arcfra Team

Last edited on 2026-09-15

Introducing the Arcfra Data Protection Adapter — bringing Veeam and Commvault protection to Arcfra workloads today, while native integration matures.

As organizations move beyond VMware, many are adopting new virtualization and enterprise cloud platforms on a faster timeline than the backup ecosystem can fully support. That creates a practical data protection gap: customers want to modernize their infrastructure, but they still rely on mature backup platforms such as Veeam and Commvault. Native integrations remain the long-term goal, but they take time to build, certify, and support.

To help customers protect workloads today, Arcfra has introduced the Arcfra Data Protection Adapter, which connects Arcfra Enterprise Cloud Platform (AECP) with existing Veeam and Commvault deployments so teams can keep using the backup tools, policies, and workflows they already trust. Together with Arcfra Backup and Disaster Recovery (ABDR), enterprise users can choose the right data protection path tailored to each workload needs.

Recovery stopped being an IT chore

Somewhere in the last few years, backup quietly changed jobs. It used to be insurance. It is now a security control — the one that decides whether a bad day becomes a bad quarter.

Attackers understood this before most boards did. Veeam’s research found 96% of ransomware attacks target backup repositories, and 76% of those attempts succeed. Encrypting production is only half the plan; the other half is making sure you cannot come back.

The gap between believing you can recover and proving it is the whole game. Veeam’s Data Trust and Resilience Report 2026 found 90% of organizations confident they could recover from a cyber incident — and only 28% of ransomware victims who actually recovered all their data.

The post-VMware era created a real problem for backup vendors

Not long ago, enterprise virtualization was effectively one platform. Today it is genuinely plural: Nutanix, Proxmox, Hyper-V, OpenShift Virtualization, a range of KVM distributions, and enterprise cloud platforms like Arcfra. For customers, that choice is overdue and welcome.

For backup vendors, it is a hard engineering problem.

Supporting a hypervisor is not a checkbox. It means snapshot semantics, changed-block tracking, disk transport, guest quiescing, every restore path, and then the certification, QA and support processes standing behind all of it. Veeam and Commvault have built deep, mature integrations over many years — and they are now working through a platform list that expanded faster than anyone planned for. Engineering capacity is finite. Certification cycles run on their timelines, not on your migration schedule.

That leaves customers in an awkward middle: you have chosen an infrastructure platform on its merits, and the data protection tooling you have trusted for a decade hasn’t caught up to it yet.

Arcfra’s answer: work with backup vendors, and bridge the gap now

We are taking two paths at once.

The long-term destination is native integration, and Arcfra is engaging directly with backup vendors to get there. That is the right outcome for everyone, and it takes the time it takes.

In the meantime, our customers still have production workloads, retention obligations and audits. So we built the Arcfra Data Protection Adapter to bridge the gap between Arcfra and backup solutions from Veeam and Commvault.

How it works

Rather than ask every backup vendor for a bespoke Arcfra integration, the adapter speaks of an interface they already invested in — the oVirt/KVM management API. Veeam and Commvault both maintain mature data protection for that platform type; it is the same path used by Red Hat Virtualization and Oracle Linux Virtualization Manager. The adapter presents your Arcfra Cloud Operating System (ACOS) clusters through it.

Practically, that means the adapter runs as an ordinary containerized Linux VM inside your cluster. Veeam adds it as an oVirt KVM Manager. Commvault adds it as a Red Hat Virtualization hypervisor. Your admins keep the consoles, the job model and the muscle memory they already have — and your backup software, repositories, retention policies and reporting stay exactly as they are.

The adapter is built, tested and supported by Arcfra.

What you can do with it

Agentless full-VM backup — full and incremental, on your existing schedules. Nothing installed inside protected VMs.
Flexible recovery — restore to the original VM or rebuild as a new one, into the original ACOS cluster or a different one.
Cross-platform recovery — through Veeam, restore VMware VM backups onto Arcfra, and Arcfra VM backups back to VMware. Your backup tool becomes a migration tool, with a rollback path built in.
File-level recovery and backup verification for supported configurations.
Everything else stays put — scheduling, retention and GFS, deduplication, encryption, immutability, reporting and compliance evidence remain entirely with your backup product.

Alongside ABDR, not instead of it

To be noted, ABDR remains the fastest path for customers who want native protection managed directly from Arcfra Operation Center. The Data Protection Adapter is for organizations whose backup platform is a corporate standard, mid-contract, or embedded in audit evidence.

Available now

The Arcfra Data Protection Adapter 1.0 is available today for ACOS 6.1 and later, managed by Arcfra Operation Center 4.7.0 and later. It works with Veeam Backup & Replication 12.2+ and 13.0, and Commvault 11.40 LTS.

A fragmenting hypervisor market shouldn’t mean waiting for your data protection to catch up. Talk to your Arcfra team about protecting Arcfra workloads with the tools you already trust.