PLATFORM CAPABILITIES

Built for migrating off VMware - or around what you already run - and for staying protected after

Review the supported migration and disaster recovery paths, plus Protection and operational controls. Protection is separately licensed; each route has its own available operations.

Migrate without guest agents

Move workloads across supported platforms with controlled cutover and clear transfer progress.

Keep recovery copies ready

Repeat synchronization and test failover on supported DR paths.

Protect from one appliance

Manage migration, replication and separately licensed encrypted backup workflows in one place.

Supported migration & DR paths

These are the established migration and disaster recovery workflows available in the application. Only the combinations shown here are advertised as supported routes.

SourceDestinationMigrationDisaster recovery
VMware (vCenter/ESXi)ProxmoxYesYes - scheduled sync, failover, test failover, failback
VMware (vCenter/ESXi)VMware (another ESXi host)Yes—
OpenStack BetaProxmoxYesYes - scheduled sync, failover, test failover (no failback to OpenStack)
OpenStack BetaOpenStack (another endpoint)Yes - first copy, scheduled sync, cut-over—
ProxmoxProxmox (another node/cluster)YesYes - scheduled sync, restore points on the replica, failover, test failover (no failback - the original VM stays where it is)
Hyper-VProxmoxYes - first copy, repeat syncs and cut-over (a running VM is copied from a checkpoint); change tracking copies only the blocks that changedYes - scheduled sync with change tracking, failover, test failover (no failback to Hyper-V)
Hyper-VHyper-V (another host)—Orchestrates Hyper-V's own native Replica: initial sync, test / planned / unplanned failover, reverse, health
Nutanix AHV BetaProxmoxYes - first copy, repeat syncs and cut-over (a running VM is copied from a snapshot)Yes - scheduled sync, failover, test failover. With Prism Central, Nutanix's own changed-region tracking means only changed data is written
Nutanix AHV BetaNutanix AHV (another cluster) NewYes - first copy, repeat syncs and cut-over that starts the migrated VMYes - scheduled sync into a powered-off standby VM, failover, test failover with network adapters disconnected (no failback yet)
Linux KVM (libvirt)ProxmoxYes - first copy, repeat syncs and cut-over (a running VM is copied from a disk-only snapshot)Yes - scheduled sync, failover, test failover
Linux KVM (libvirt)KVM (another host)Yes - first copy, scheduled sync, cut-over—

A dash means that operation is not advertised for the selected route. Beta identifies integrations that require validation on your particular hypervisor and storage versions; test with a disposable VM before moving important workloads. Feature availability also depends on licensing and destination prerequisites.

Disklift job window for a Hyper-V to Proxmox cut-over showing progress and throughput
A Hyper-V to Proxmox replication job in progress: percent done, data copied, throughput, time remaining and the source hypervisor latency while it ran (sample data).
LIVE JOB VIEW

Know exactly where every migration stands

Every job opens into one window: how far along it is, how much has been copied, how fast, and how long is left. You can tell a slow disk from a slow network because the hypervisor latency during the job is drawn right underneath the throughput graph.

  • Progress, GiB copied and time remaining, updated while the job runs
  • Throughput in MB/s and Gbps with a live graph of the current phase
  • Source and destination hypervisor latency during the job, not an hour later

What you gain: plan your cut-over window from measured numbers instead of guesses, and spot a struggling host before the weekend is over.

Disklift Hyper-V host inventory listing virtual machines, their generation, disks and replication state
A Hyper-V host's inventory: each VM with power state, hardware generation, disks and format, replication and checkpoint state (sample data).
HOST INVENTORY

See what is on the host before you move it

Register a Hyper-V host and Disklift lists its virtual machines with their state, hardware generation and configuration version, disks and disk format, and any Hyper-V replication or checkpoints.

  • Generation 1 and 2 VMs, VHD and VHDX disks identified up front
  • Replication and checkpoint state visible per VM
  • Power state and VM identifier listed per VM

What you gain: fewer surprises on cut-over night, because you know what each VM looks like before the first byte is copied.

Disklift policies filtered to Nutanix AHV: an AHV to AHV disaster-recovery policy next to an AHV to Proxmox policy, with replication state and RPO
Nutanix AHV to AHV next to AHV to Proxmox: each standby VM shows Replicated, its measured RPO against the target, when it last synced and when the next sync runs (sample data).
DISASTER RECOVERY

Standby copies you can see are current

Disaster-recovery policies keep a powered-off standby VM refreshed on a schedule. Each row shows whether the replica is current, how far behind it is against the recovery-point target you set, and when the next sync runs. Planned failover and Sync now are one click away.

  • Measured RPO next to the target (for example 12m 49s of 30m)
  • Last replica age and next sync time per VM
  • Planned failover and test failover from the same screen, with test failover starting the replica with network adapters disconnected

What you gain: prove your recovery point to an auditor at a glance, and rehearse failover without touching production.

Agentless block-level copy

Move VMs between the source and destination pairs in the supported matrix without deploying a Disklift agent inside every guest. Use the wizard to check supported storage, controller and network mappings before copying.

  • VMware over the vSphere API, to Proxmox or another ESXi host
  • OpenStack over API and SSH, with Ceph, LVM, or NFS backend support, to Proxmox or another OpenStack endpoint
  • Nutanix AHV through Prism, to Proxmox or to another AHV cluster (beta) - with Prism Central, only the regions Nutanix reports as changed are written
  • Nutanix AHV to AHV: the replica's disks are written as files into the destination storage container, and a powered-off standby VM gets instant clones of them after every complete sync - a sync that stops half-way never touches it
  • Linux KVM (libvirt) over SSH, to Proxmox or another KVM host - a running VM is read from a short-lived disk-only snapshot that is merged back afterwards
  • Proxmox → Proxmox moves, for consolidating or rebalancing clusters you already run

Thin copy, changed blocks, compression & deduplication

Only the data that matters crosses the wire: after the first copy, changed-block tracking ships just what changed, and empty blocks are skipped where the destination is already zeroed. No extra SKU to buy.

  • Repeat syncs and the final cut-over move only the changed blocks, for migration and DR alike
  • Optional zstd wire compression per policy (off by default) - used when both ends have zstd, otherwise the copy simply runs uncompressed
  • Optional deduplication per policy (off by default): on the first copy to Proxmox, a 1 MiB block already on the node - earlier in the same disk or from another VM in the policy - is copied locally on the node instead of being sent again. Every local copy is read back and checked, and anything doubtful is sent normally
  • Measured efficiency shown in one-decimal ratios (for example, 2.2x) per job and on the performance dashboard: the thin-copy ratio, the compression ratio when it is on, and the deduplicated bytes when deduplication is on. With it off, the job still shows how much of the data repeated, so you can see whether it would pay off

Online, offline, or with a safety clone

You choose how each source is read: migrate a running VM while it stays in production, shut it down first for the cleanest copy, and optionally keep a full safety clone of the original.

  • Online (recommended): the VM keeps running. For VMware, a snapshot freezes the disks and changed-block tracking ships only what changed, so downtime is limited to the cut-over
  • Offline: the VM is shut down before the first copy and stays off - the cleanest copy, with downtime from the start
  • Cut-over: optional graceful shutdown of the source, a final sync, checksum verification, then the new VM is powered on (or left off for you). The original is kept until you choose to delete it
  • Optional safety clone (VMware): a thin, powered-off, network-disconnected copy with new MAC addresses, made before cut-over. Off by default; a running VM is copied crash-consistently with no downtime, and if the clone fails the migration does not start
  • Destination space is checked before a copy starts, with a warning if it won't fit. Temporary snapshots and clones are removed after failed or cancelled jobs; a safety clone is only ever deleted by you

Scheduling & policies

Group VMs into policies with their own schedule, bandwidth limits, and retry behavior, instead of kicking off every migration by hand or writing your own cron jobs.

  • Per-policy bandwidth caps so a migration doesn't starve production traffic
  • Inventory refreshes run as a staggered background job, never on demand mid-wizard

Live performance dashboard

Throughput, jobs per hour, thin-copy, compression and deduplication savings, and job health across every migration and replica in flight, with history from real time out to 90 days - not just a progress bar.

  • Average RPO and (once you've had a failover) average RTO, both from real measurements
  • Per-job phase breakdown to the millisecond, so a slow run shows you exactly where the time went
  • Live hypervisor latency in milliseconds, datastore and CPU counters, and any custom time range with drag-to-zoom

Disaster recovery mode

For VMware, OpenStack, Hyper-V, Nutanix AHV and Linux KVM, keep replicating after cutover: scheduled sync, failover and test failover to Proxmox - plus failback for VMware - and Nutanix AHV to another AHV cluster - licensed per protected seat, billed annually, running on the same install as your migrations.

  • Test failover without disrupting the production replica or resetting its sync
  • RPO tracked live against each policy's sync interval, with a breach alert
  • Hyper-V to Hyper-V is protected a different way - Disklift orchestrates Hyper-V's own native Replica directly (initial sync, test/planned/unplanned failover, reverse, health) - same licensing, no separate console

Role-based access & 2FA

Admin / operator / read-only roles, two-factor authentication via any TOTP app (Google Authenticator, Microsoft Authenticator, Duo, or similar), and a full audit log of who changed what.

  • Repeated failed logins to a hypervisor stop automatically, so a changed password doesn't lock the account out

Encrypted at rest

Hypervisor credentials, SSH keys, and other secrets are encrypted at rest with rotatable keys - never stored in plain text, and only ever decrypted in memory for the duration of a job.

  • License signing is handled by a separate internal service - never internet-facing

Down to the millisecond

See what a hypervisor is doing while a migration runs - not an hour later. Live latency every 5 seconds, the hypervisor's own datastore and CPU counters, and any time range from 10 seconds to 90 days.

Disklift measures connect time and API round trip in milliseconds for VMware, Proxmox, Hyper-V and OpenStack, plus datastore and CPU counters where the platform reports them
Live hypervisor latency chart in milliseconds for each hypervisor with median, 95th percentile and worst values
Live view: API round trip for each hypervisor every 5 seconds, with latest, median, 95th and 99th percentile and the worst value (sample data).
LIVE LATENCY

Spot a slow hypervisor while the job is still running

Open the Performance page in Live mode and Disklift measures every registered hypervisor every 5 seconds. Pick the hypervisors to compare, read the percentiles in the table, and see spikes that a five-minute average would hide.

  • Connect time and API round trip, in milliseconds, per hypervisor
  • Median, 95th, 99th percentile and worst value, with the sample count
  • Works across VMware, Proxmox, Hyper-V, OpenStack, Nutanix and KVM sources

What you gain: you find the host that is slowing your migration in seconds, and you have numbers to show the platform team.

Datastore read latency per hypervisor from the hypervisors' own counters
Datastore latency and CPU straight from each hypervisor's own counters, drawn for its slowest datastore or disk (sample data).
THE HYPERVISOR'S OWN COUNTERS

See storage pressure, not just network delay

Beyond the round trip, Disklift reads the counters the hypervisors keep themselves. Each line is one hypervisor drawn for its slowest datastore (VMware) or disk (Hyper-V), so the cause of a slow copy is visible.

  • VMware datastore read / write latency and CPU; Hyper-V disk latency, disk queue and CPU
  • Proxmox CPU and I/O wait; Proxmox has no latency counter, so none is invented
  • The chart keeps the worst value of each interval, so a spike is never averaged away

What you gain: a clear answer to whether the bottleneck is the network, the source storage or the host CPU.

Monitoring settings: measure only while someone is looking, every 30 seconds, or every 5 seconds, with a warning about load and API limits
Monitoring settings: only while someone is looking (the default), every 30 seconds or every 5 seconds, plus how long to keep history (sample data).
YOU CHOOSE THE LOAD

Measure as often as you like, with the cost spelled out

Out of the box Disklift measures only while someone has a Performance page open, so nothing extra reaches your hypervisors otherwise. If you want history in seconds even when nobody is watching, you can switch to every 30 or every 5 seconds, and set how long history is kept.

  • Default: measure only while someone is looking, one sample every 5 seconds
  • Optional always-on modes every 30 or 5 seconds
  • History kept for 90 days by default, with a built-in estimate of what it will cost

What you gain: no surprise load on production hypervisors, and no surprise database growth.

Measured honestly

  • Connect time (TCP + TLS) and one API round trip on an already-open session - no login per probe
  • VMware datastore read / write latency and CPU; Hyper-V disk latency and CPU; Proxmox CPU and I/O wait (Proxmox has no latency counter, so none is invented); OpenStack reports none
  • The chart keeps the worst value of each interval, so a spike is never averaged away
  • Each job shows its own phases in milliseconds and the latency of its source and destination while it ran

Protection: scheduled VM backups into storage you own

A separately licensed option. Back up VMware, Hyper-V, Proxmox, OpenStack and Nutanix AHV (beta) VMs on a schedule into encrypted, deduplicated restore points kept in your own NFS, S3-compatible or host-mounted iSCSI/FCoE storage - from the same appliance, with nothing installed in the guests. Restore them as disk files or as a new VM, and let the ransomware guard watch every backup.

Disklift Protection policies: schedule, retention, VMs and last run
Policies: which host and repository, the schedule, next and last run, retention, speed limit and the VMs covered, with Run now, Edit, Pause and Remove on each card (sample data).
BACKUP POLICIES

Set the schedule once and let it run

A policy says which VMs of one host are backed up into which repository, and when: daily on the weekdays you choose, or every N minutes. Retention, stream count and speed limit are set per policy, and the first run of a VM is a full copy while later runs store only what changed.

  • Next run and last result visible on every policy card
  • Run now, edit, pause the schedule or remove, without leaving the page
  • Retention by number of restore points, plus a periodic whole read to keep everything honest

What you gain: predictable protection with no agents inside the guests, no scripts and no cron jobs.

Disklift Protection activity: running and recent backup runs with progress and rates
Activity: a running backup with progress, read and write rates and time left, above the history of recent runs with duration, data covered, newly stored and reused (sample data).
BACKUP ACTIVITY

Watch every backup as it happens

Active runs update every few seconds: percent done, the rate read from the VM against the rate sent to the repository, operations per second, VMs finished and time left. Below that, every recent run with its result, duration and how much of the data was new.

  • Cancel a run, or open its per-VM results, log and throughput graph
  • Newly stored versus reused shows deduplication working run by run
  • Search and filter runs by policy, repository, host or result

What you gain: you find out about a problem while it is happening, not the next morning.

Disklift Protection performance: space used, deduplication savings, throughput and I/O charts
Performance: policies, protected VMs, restore points, data covered versus data stored, space saved, and each repository with its free space (sample data).
CAPACITY AND SAVINGS

See what protection costs, and what it saves

The Performance tab turns the repository into numbers: how many VMs are protected, how many restore points exist, how much VM data they cover and how much was actually stored after deduplication. Filter by time range, repository or policy.

  • Space saved by deduplication, as a percentage you can check
  • Per-repository state, restore points, stored size and free space
  • Throughput and I/O charts for the time range you pick

What you gain: capacity planning from measured figures rather than estimates.

Disklift restore points of one VM: the newest is quarantined because its data looks encrypted, the earlier ones are OK
Ransomware guard: the newest restore point is quarantined because nearly all of its data is new and looks encrypted; earlier points stay OK. An administrator can release or remove it (sample data).
RANSOMWARE GUARD

Do not restore a poisoned backup by accident

Disklift compares every new restore point with the history of that VM. If almost all of the data is new, cannot be deduplicated against earlier points and looks encrypted, the restore point is quarantined and shows the reasons. It waits for an administrator to release it or remove it.

  • The reason is shown in plain numbers: share of new data and how much of it looks encrypted
  • Earlier restore points stay available while the suspect one waits
  • Check, Deep check, Release and Remove sit beside the point

What you gain: one quarantined backup instead of a restore that brings the problem back. Detection needs baseline backup history and complements your other security controls.

Disklift Protection repositories with staged health checks, free space and days of space left
Repositories: state, location, free space, encryption (AES-256-GCM with a key fingerprint), last check, capacity and space saved, with Verify now, Self-test and Recovery bundle (sample data).
BACKUP REPOSITORIES

Know your backup storage is healthy before you need it

Each repository, whether an NFS share, S3-compatible bucket or mounted SAN storage, shows its state, free space, restore-point count and last check. Restore points are encrypted, and the card tells you whether the share protects them from deletion. A repository that fails its check holds runs instead of failing them.

  • AES-256-GCM encryption with the key fingerprint shown
  • Verify now and a self-test whenever you want proof it works
  • A recovery bundle so the repository can be reopened elsewhere

What you gain: confidence that the backup you will need on the worst day is readable.

  • Backup policies for VMware, Hyper-V, Proxmox, OpenStack and Nutanix AHV (beta) in one place: run on demand, every N minutes, or daily on the weekdays you choose
  • Changed blocks only: after the first restore point of a VM, a run reads only what the hypervisor reports as changed (VMware CBT, Hyper-V resilient change tracking, Proxmox ZFS / Ceph, Nutanix changed regions with Prism Central) and takes everything else from the previous point. Every restore point stays complete on its own, unchanged chunks are spot-checked against the source, and a whole read runs every N days (7 by default)
  • Run now for the VMs you choose - or let the schedule do the whole policy
  • Fills the link to S3: uploads run in parallel with the reading (16 at a time by default), so a distant S3 region is no longer limited to one connection's speed; a block is recorded only after the repository confirmed it
  • Retention by count and by age - newest N, every point for N days, then one per week, month and year; the policy shows how many points are beyond it
  • Activity (running runs, recent runs and events) and Performance views: progress, read and write rates, repository requests per second, time left, space used, deduplication savings, throughput and I/O history for 90 days - narrowed to one policy if you like
  • Search, filters and pages everywhere: policies, repositories, runs, events, restore points, restores and live mounts - with cards that collapse, for estates with many policies
  • Alerts for failed and completed runs to Teams, e-mail and syslog, and every action in the audit log
  • Ransomware guard: every backup is compared with the earlier ones of the same VM - how much of the data is new, how random (encrypted-looking) it is, and whether the amount of data dropped. One signal marks a restore point suspicious; two or more quarantine it so it cannot be restored until an administrator releases it (after a check of its data) or removes it. Nothing is deleted automatically, and every decision is audited and can alert you
  • Restore a restore point as disk files (raw, qcow2, vmdk, vhdx) to an NFS share, a remote host over SSH or an S3 bucket - or as a new VM on Proxmox, VMware, Hyper-V, OpenStack or Nutanix AHV (beta), with a safe default of not connecting the network. Restores stream straight to their destination: nothing is staged on the appliance, so even a very large VM never fills it
  • Live mount: open a restore point's disks read-only over NBD with TLS, an allow-list of client addresses, secret export names and a time limit - nothing is copied first. On a Proxmox node or KVM host the appliance can also do the rest: mount the file systems read-only, or create a test VM (powered off or started) on copy-on-write overlays with its network cards disconnected; everything is removed from the host when the mount ends. Ended mounts can be hidden from the list and brought back
  • Back up OpenStack VMs too (Ceph, LVM and NFS volumes over SSH, or API-only)
  • Immutability with S3 Object Lock: the appliance checks that Object Lock is on and in which mode, warns when it is not, and cannot remove a restore point the bucket keeps locked. A network share cannot be made immutable by the appliance - use snapshots with retention on the file server
  • Encrypted at rest with AES-256-GCM; manifests are signed, so a changed or swapped file is detected and refused when read
  • Verified when you connect and before every run; a repository that fails is held and the run waits, instead of failing
  • An interrupted run resumes and re-checks what it already stored - from a fresh snapshot, so a restore point is always one consistent moment; the encrypted recovery bundle restores access if the appliance is lost

For supported instant-access recovery, use read-only NBD restore-point presentation and the Proxmox/KVM attachment workflow. The ransomware guard compares a workload against earlier backups; it complements, rather than replaces, your security controls.

RECOVERY & OPERATIONS

Operate and recover with the tools already in Disklift

Recovery access, troubleshooting, network visibility and performance information are part of the appliance's daily workflows.

Live restore-point access

Present protected disks read-only through an authenticated NBD mount with TLS, an allowed-client list and expiration. On Proxmox and Linux KVM hosts, create an isolated test VM with copy-on-write storage or inspect files without altering the original backup.

Protection & transfer efficiency

Track logical versus stored backup bytes, combined storage reduction, and measured Migration/DR wire reduction and deduplication. Ratios use a readable one-decimal display, such as 2.2x; missing measurements are shown as unavailable.

One Test Hypervisor workflow

Admin troubleshooting checks connectivity, inventories and applicable storage and journal capabilities, recording PASS, FAIL or SKIP in the downloadable support bundle. A skipped migration or guest-boot check is not marked successful.

LLDP & Cisco CDP network discovery

Read nearby interface and switch details from the host's receive-only discovery agent. View neighbors per Management, Data or Backup interface and include available network details in support diagnostics.

Built for enterprise estates

Everything above runs the same on a small lab or a large data center. For bigger estates, Disklift adds the scheduling, resilience and operational controls that long, busy migrations depend on.

Fair, predictable scheduling

Cut-overs and failovers always go first, then first copies, then routine syncs. Work is shared fairly between policies, limits protect every source host and destination node, and sync times are spread out so hundreds of VMs never all come due at once.

Scale out, not just up

Add worker capacity with a single command as the estate grows. A queue-wait view and an alert tell you before waits start to threaten your recovery targets - and the documentation includes a sizing guide.

Keeps going when things break

Restarts and upgrades let running jobs finish cleanly. A database outage does not lose results. An interrupted first copy continues where it stopped, and the part already copied is re-checked against the source.

Self-managing storage

Old job history and logs are cleaned up automatically, the appliance warns before its disk fills, and the destination is checked before a copy begins and watched while it runs. Disk data streams through the appliance and is never staged on it, so its disk does not grow with the size of your VMs.

Its own network for the data

Keep replication and backups off your management network: add adapters to the appliance and put them on data or backup networks - one adapter or an LACP bond, with VLAN tags, jumbo frames and live link statistics. Each hypervisor and repository can be reached on its data address. How to set it up.

Operations-ready

Health checks for every service, optional metrics for your monitoring system, support for a highly available PostgreSQL, and encrypted off-site copies of the appliance's own backups.

Signed upgrades, checked for you

The appliance checks for a newer version once a day (you can switch that off), downloads it with progress, and verifies the file's SHA-256 and the vendor's digital signature before the Apply button appears. Applying takes a database and files backup first, installs, restarts and runs a self test - and an upgrade is reported as done only when the running application reports the new version. Your open browser tab reloads itself onto the new release.

Releases only for licensed installations

There is no public download. A short-lived link is issued only to an installation with a valid licence, and the check sends nothing more than the installation ID, the installed version and the licence file. The host re-verifies the signature with its own copy of the vendor's key and refuses anything that is not strictly newer.

Secure by design

Role-based access, two-factor sign-in, a full audit trail, encrypted credentials and strict separation of tenants and data - the controls security teams ask for, in the box.

  • Jobs are prioritised and limited per host, so production hypervisors are never swamped by migration traffic
  • Throughput scales by adding workers; the documentation gives starting sizes for small, medium, large and enterprise deployments
  • Designed so that no single failure - a restart, a lost connection, a database blip - silently loses work

See the recommended sizing, or talk to us about a large estate.

How it compares

Most tools in this space were built for one job and bolted the other on. Disklift is built for the move to Proxmox specifically, with DR as a first-class second act - not the reverse.

 DiskliftZertoVeeam
Proxmox VE as a targetCore product - migration and DRNot supported (VMware vSphere, Hyper-V and public clouds)Yes - backup and restore since 2024; VM replication added in v13.1
Moving VMs to ProxmoxDirect block-level copy with repeat syncs, then a short cut-over - no backup stepNot a Proxmox migration pathYes - restore VMware / Hyper-V backups to Proxmox (a backup first; Instant Recovery added in v13.1)
Source platformsVMware, Hyper-V, OpenStack (beta), Nutanix AHV (beta), Linux KVM, ProxmoxVMware vSphere, Hyper-V, public cloudsThe broadest list - VMware, Hyper-V, Proxmox, Nutanix AHV and more
Disaster recovery replicationScheduled, change-tracked syncs (minutes) with failover and test failoverContinuous, journal-based, recovery points seconds apart - its core strengthSnapshot-based replication jobs
Cutting data sent over the wireChanged-block tracking, empty-block skipping, optional zstd compression, and optional verified deduplication on the first copy to Proxmox - built in, no extra applianceWAN compression and signature matching to reduce data sent over the WANCompression, plus WAN acceleration with global deduplication - needs a WAN accelerator pair and an Enterprise or Universal license
Scheduled VM backupsProtection option: VMware, Hyper-V, Proxmox, OpenStack and Nutanix AHV (beta) VMs on a schedule into encrypted, deduplicated restore points in NFS or S3, with count and age-based retention, activity and performance viewsNot its focus - recovery is journal-based replication; long-term retention is a separate part of the productThe core product - mature backup, retention and instant recovery
RestoringTo disk files (local, NFS, SSH, S3) or to a new VM on Proxmox, VMware, Hyper-V, OpenStack or Nutanix AHV - a full copy-back; or live-mount a restore point's disks read-only over NBD without copying themFailover and recovery to a chosen point in time, to its supported platformsFull restore, cross-platform restore and instant recovery (run a VM straight from the backup)
Ransomware protectionEach backup is scored against that VM's own history (change rate, entropy, deduplication, size); suspicious ones are flagged and quarantined for an administrator to release or remove. S3 Object Lock status is checked. It is new and learns only from your own backups - there is no malware-signature databaseRecovery to a point seconds before an attack, plus long-term retention with immutability optionsImmutable repositories, malware detection and instant recovery are established, mature features
Backup encryption and deduplicationAES-256-GCM, signed manifests, deduplication per repository, built inEncryption and compression for replicated dataEncryption and deduplication, with global deduplication on higher editions
What you deployOne appliance VM; nothing on hosts or in guestsA replication appliance on every hostA backup server plus a worker / proxy on hosts
Pricing modelOne-time per VM, or annual per-seat DR or ProtectionPer-VM subscription, quote-basedPer-workload subscription, tiered editions

Zerto and Veeam are trademarks of their respective owners; this comparison reflects their publicly documented capabilities as of November 2026 and isn't endorsed by either company. Veeam's support for Proxmox is documented here and its supported workloads here; HPE lists Zerto's supported platforms here. Vendors change their products - check their current documentation, and if something here is out of date, let us know and we'll correct it.

See it on your own workload

Download it free - it runs in evaluation mode with no license required (30 days, up to 5 VMs / 750 GB for migration, 3 VMs for replication - see the limits), so you can try a real migration before buying. The QCOW2 download is approximately 7.9 GiB and provides a 32 GiB virtual disk; the VMware package is separate.

One migration-center.qcow2 image serves all three platforms. View deployment steps and first-boot credentials. Image-format compatibility does not by itself certify boot on every hypervisor version.