The Real Impact of Encryption on Cloud Backup Speed
Discover how AI-driven forecasting in Comet Backup helps MSPs prevent data loss before it happens.
Virtualization makes infrastructure easier to provision and manage, but backing up virtual machines still requires careful planning.
VMware and Proxmox use different architectures and management interfaces, which means backup requirements can vary between environments. MSPs moving clients from one platform to another also need to understand how backup, storage, recovery, and operational workflows change.
The right backup strategy should account for the hypervisor, virtual machine configuration, storage architecture, recovery objectives, and available backup tools.
A virtual machine is more than its virtual disk.
A useful VM backup may need to include:
The backup platform also needs an appropriate method for accessing the hypervisor and reading VM data without unnecessary production disruption.
Comet’s VMware vSphere backup integrates directly with vCenter Server or an ESXi host. It creates a snapshot of the selected VM, streams the required files through its chunking engine, and then removes the snapshot from the host.
The backup includes VM configuration files, VMDK disks, and other required files.
Comet’s current VMware documentation lists vSphere 6.7 or later as a server requirement, while the desktop client requires Windows x86_64 and network access to the target ESXi or vCenter environment.
The backup system also requires appropriate VMware permissions to create and remove snapshots, access virtual machine disks, and browse required datastore information.
Large VM disks can generate significant network traffic during backup.
Comet recommends placing the backup software close to the ESXi cluster or host for best performance. Changed Block Tracking can also reduce the amount of data that needs to be processed after the initial backup.
Comet’s Proxmox solution supports Proxmox VE virtual machines and containers. The current Comet Proxmox solution requires the agent to be on the same network as the target Proxmox cluster and supports Proxmox VE 8.x or higher.
This is important for MSPs planning migrations because the backup environment must be evaluated alongside the Proxmox infrastructure.
Proxmox backup workflows can also use snapshot-based methods and Changed Block Tracking where supported.
| Requirement | VMware | Proxmox |
| Hypervisor | VMware vSphere | Proxmox VE |
| Backup connection | vCenter or ESXi | Proxmox cluster |
| VM support | vSphere VMs | Proxmox VMs |
| Container support | Not applicable in the same way | Proxmox containers |
| Changed Block Tracking | Supported | Supported |
| Network requirement | Same network as target environment | Same network as target cluster |
| Recovery options | VM and file-level workflows | VM and cross-platform recovery options |
Recovery planning should be evaluated before selecting a backup platform.
A backup that is easy to create but difficult to restore may not satisfy the client’s RTO.
Comet Backup supports VMware recovery workflows and can restore virtual machine components for reimport into VMware environments.
For Proxmox, Comet supports cross-platform recovery, including restoring backups to Proxmox, VMware, or Hyper-V environments.
That capability can be particularly useful for MSPs managing virtualization migrations.
Both environments can generate large amounts of VM data, making storage efficiency important.
Comet uses chunking, compression, and deduplication to avoid repeatedly storing identical data.
Backup scheduling, retention, and storage policies should still be configured according to the workload rather than the hypervisor alone.
The choice between VMware and Proxmox should not be made based solely on backup requirements.
Consider:
For MSPs, backup portability can also be important.
A provider managing clients across different virtualization platforms may benefit from a backup solution that can support multiple hypervisors through a consistent management workflow.
No. Although both protect virtual machines, the backup process, hypervisor interfaces, permissions, and recovery workflows differ.
Yes. Comet supports VMware vSphere backups through vCenter Server or ESXi connections.
Yes. Comet supports Proxmox VE virtual machines and containers. Its current Proxmox solution requires Proxmox VE 8.x or higher.
Comet’s Proxmox solution supports restoring backups to Proxmox, VMware, or Hyper-V environments.
CBT can reduce the amount of changed data that needs to be processed after the initial backup, improving backup efficiency.
VMware and Proxmox have different backup requirements, but the underlying principle remains the same: the backup architecture should support the client’s recovery objectives without creating unnecessary operational overhead. MSPs should evaluate backup connectivity, storage, performance, retention, and recovery before committing to a virtualization strategy.