PLATFORM CAPABILITIES

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

Every feature below is included in both license kinds - Migration and DR only change what you're licensed to run, not which features are turned on. See the exact source/destination pairs below.

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

Not just VMware-to-Proxmox. Here's every source/destination pair Disklift supports today.

SourceDestinationMigrationDisaster recovery
VMware (vCenter/ESXi)ProxmoxYesYes - continuous sync, failover, test failover, failback
VMware (vCenter/ESXi)VMware (another ESXi host)YesNot yet - failover/failback aren't available for this pair
OpenStack BetaProxmoxYesYes - continuous sync, failover, test failover (no failback to OpenStack)
OpenStack BetaOpenStack (another endpoint)Yes - first copy, continuous sync, cut-overNot yet - failover and test failover aren't available for this pair
ProxmoxProxmox (another node/cluster)Yes—
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 - continuous 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 - continuous sync, failover, test failover. With Prism Central, Nutanix's own changed-region tracking means only changed data is written
Linux KVM (libvirt)ProxmoxYes - first copy, repeat syncs and cut-over (a running VM is copied from a disk-only snapshot)Yes - continuous sync, failover, test failover
Linux KVM (libvirt)KVM (another host)Yes - first copy, continuous sync, cut-overNot yet - failover and test failover aren't available for this pair

Beta marks paths that are built and covered by automated tests against simulated environments, and are still being proven on live infrastructure. Hyper-V (migration, DR replication and Replica orchestration) has been validated with testing. Nutanix AHV is built from Nutanix's published API documentation and has not yet been run against a live cluster. Linux KVM runs over SSH with no agent; it has been tested with a real shell but not yet against a live libvirt host.

Disklift job window for a Hyper-V to Proxmox cut-over showing progress and throughput
A Hyper-V → Proxmox cut-over in progress.
Disklift Hyper-V host inventory listing virtual machines, their generation, disks and replication state
A Hyper-V host's inventory: VMs, generation, disks and checkpoints.

Agentless block-level copy

VMware (vCenter or standalone ESXi), OpenStack, Nutanix AHV and Linux KVM sources, moved to Proxmox - or to another VMware, OpenStack or KVM endpoint - without installing anything inside the guest. No agent to deploy, license, or clean up afterward.

  • 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 (beta) - with Prism Central, only the regions Nutanix reports as changed are written
  • 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
  • Live savings shown 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 and OpenStack, keep replicating after cutover: continuous sync, failover, test failover and failback to Proxmox or another endpoint - 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 ten hypervisors with median, 95th percentile and worst values
Live view: API round trip per hypervisor, with median, 95th / 99th percentile and the worst value (sample data).
Datastore read latency per hypervisor from the hypervisors' own counters
Datastore latency and CPU straight from the hypervisor's counters (sample data).

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
Monitoring settings: measure only while someone is looking, every 30 seconds, or every 5 seconds, with a warning about load and API limits
You choose the load: only while someone is looking (default), every 30 s, or every 5 s - with the risk spelled out.

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 or S3 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 VMs, where, when, and how long to keep them (sample data).
Disklift Protection activity: running and recent backup runs with progress and rates
Activity: running and recent runs with progress, speed and time left (sample data).
Disklift Protection performance: space used, deduplication savings, throughput and I/O charts
Performance: space used, deduplication savings, throughput and I/O over time (sample data).
Disklift restore points with a quarantined, a suspicious and a released restore point
Ransomware guard: a backup that looks encrypted is quarantined until an administrator releases or removes it (sample data).
Disklift Protection repositories with staged health checks, free space and days of space left
Repositories: every stage of the connection check, free space and a forecast (sample data).
  • 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
  • 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 and Performance views: progress, read and write rates, time left, space used, deduplication savings, throughput and I/O history for 90 days
  • 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 on another machine over NBD, with TLS, an allow-list of client addresses, secret export names and a time limit - nothing is copied first
  • 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; the encrypted recovery bundle restores access if the appliance is lost

Still to come: starting a VM straight from a restore point, automatic pruning, and second-administrator approval for deletes. The ransomware guard needs a few earlier backups of a VM before it can tell what is normal; it is a safety net, not a guarantee.

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 download is a ready-to-run appliance image of about 7 GB.