Snapshot
A recovery point within your production environment, dependent on source resources.
Same storage environment
Behind every virtual machine is a business that needs to keep moving. With BackupONE, you plan your backups, keep a separate copy and prepare a clear route back to work.
Protection tailored to your environment

Choose what matters, select your storage destination and manage recovery points. Your backup stays separate from your production environment, ready when you need it.
This diagram shows possible backup destinations. Your design determines how they work together. Automatic replication to an additional destination depends on the version and edition and is listed as beta on some product pages.
Choose a platform to explore its backup approach. Available options depend on the system, version and licensing.
The backup agent runs on a Windows computer and connects to the ESXi host over the network. Select the relevant machines and disks without installing a backup agent inside every VM.
VMware Tools supports application consistency within the guest operating system.
The backup agent runs on the local Hyper-V host, protecting its virtual machines with a plan tailored to your business.
A managed edition lets you configure and monitor plans through a management console.
A Windows agent connects to the host through the Proxmox API and backs up VMs to a supported destination. This process does not require Proxmox Backup Server.
Select VMs to back up. Individual disk selection is described as a future capability.
| What should you check? | VMware | Hyper-V | Proxmox |
|---|---|---|---|
| Backup agent location | Windows with ESXi access | Local host / cluster node | Windows with API access |
| Backing up changes | CBT | RCT on supported systems | Incremental backup |
| Selecting individual VM disks | Supported | Check the plan configuration | All attached disks |
| VM or item recovery | Supported, depending on recovery method | Supported, depending on recovery method | Supported in current documentation |
| Encryption and scheduling | Supported | Supported | Supported |
| Synthetic full backup | Depends on plan and storage | Depends on plan and storage | From 8.6.5, with supported storage |
Incremental backups transfer the blocks changed since the previous backup. In VMware, CBT helps identify them without reading the entire disk on every run.
The first backup establishes the baseline. Subsequent backups retain changes according to the plan type and system support.
Source disk
Changes to transfer
6 blocks ready to transfer
Conceptual example only. The number of blocks shown does not represent actual performance or storage savings.
A snapshot helps you return to an earlier state, for example before an update. If it relies on the same host and storage, a failure there may affect it too. An independent backup is stored separately and can be used to rebuild the machine.
A recovery point within your production environment, dependent on source resources.
Same storage environment
A copy stored outside the source environment, with recovery points.
Separation reduces dependence on the source
From critical machines to email alerts, these are the decisions that shape your backup plan.
Select the machines that matter to your business.
Machine names are examples for illustration.
Illustrative interface, not a product screenshot. Actual steps and options vary by platform and version. VMware guide · Hyper-V guide
Choose what to restore, from which point and to which destination. Then verify that your data and applications are in the required state.
Restore the operating system, applications and data from a backup point. Choose a suitable host and storage destination, then test the machine before returning it to service.
Selected point: Monday, 08:00. Start the illustration when ready.
VMware, Hyper-V and Proxmox have separate recovery workflows. This does not imply automatic conversion between every platform.
VMware recovery lets you choose a new name or overwrite an existing machine and select a datastore. Check the destination and VM state carefully before overwriting.
The recovery processA suitable system backup can be converted into a virtual disk and attached to a new Hyper-V or VMware machine. Boot settings, controllers and licensing must be checked.
About P2V recoveryAnother workflow restores an image-based backup as a VMware VM, with a choice of resources, network and storage. Verify support in your edition and version.
Restore to vSphere
A backup stored only on the source server shares the same point of failure. Plan an additional copy in a separate location.
Enable encryption and store recovery credentials securely. Object Lock can add protection where supported by the edition and storage destination.
Check that the VM boots, applications work and files are intact. A successful backup notification is a start; a recovery test provides a fuller picture.
The details matter when adapting backup to your environment.
Host-level backup does not require a separate backup agent inside each VM. For VMware and Proxmox, a Windows agent connects to the host over the network. For Hyper-V, it runs on the local host or a suitable node. Guest components such as VMware Tools may be needed for application consistency.
Yes. Supported item-level recovery workflows let you select files and folders from a backup instead of restoring the whole VM. Check file system, backup type and version compatibility before deployment.
This is a standalone vendor edition, separate from the BackupONE service offering. The source information lists a limit of one host, up to two CPU sockets and up to 5 TB of backup storage, with community support. Commercial licensing and service packages are arranged separately. Edition details and limitations
Recovery time depends on data volume, storage, network and destination resources. Instant Restore was listed as beta on the reviewed Hyper-V page, so it is not presented here as a service guarantee. Define a recovery time objective and test it in your actual environment.
Base retention on data change rates, business importance and organizational requirements. Choose a backup frequency and retention policy that also covers incidents discovered later, and size your storage accordingly.
Map your hosts and VMs, identify critical applications and decide how much data loss and downtime you can tolerate. Then build a plan, run the first backup and test recovery.
VMware, Hyper-V או Proxmox? נכיר את הסביבה שלכם ונתכנן גיבוי ושחזור שמתאימים לעסק. כדי שברגע האמת תהיה תכנית, ולא רק מישהו שיגיד ״ניסיתם לכבות ולהדליק?״