דילוג לתוכן
Virtual machine backup and recovery

Virtual machines.
Your peace of mind is real.

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

VMwareHyper-VProxmox
Complex technology.
Clearly explained.
IT professionals alongside a computer system, server and backup cloud
The bigger picture

Your data needs
a safe place to recover from.

Choose what matters, select your storage destination and manage recovery points. Your backup stays separate from your production environment, ready when you need it.

BACKUP FLOW / CONCEPT DIAGRAM
Production environmentOperating systems, applications and data
BackupONE
Your backup planSelection · Encryption · Scheduling · Retention
Local storageDisk, NAS or network share
Cloud storageA copy outside the source environment

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.

Select to see the backup journey
Three environments. A tailored approach.

Which platform do you need to protect?

Choose a platform to explore its backup approach. Available options depend on the system, version and licensing.

One goal.
A different route for each platform.

Back up your vSphere environment remotely.

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.

  • Back up all machines, running machines or a selected list.
  • Use CBT to identify blocks changed between backups.
  • Application-consistent backups for supported applications using VMware Tools.
Appropriate vSphere permissions and licensing are required. Check compatibility with your ESXi version before deployment.
Remote, host-level protection
Backup agentWindows computer
ESXi / vSphere
VMVMVM

VMware Tools supports application consistency within the guest operating system.

Capabilities at a glance A concise comparison
What should you check?VMwareHyper-VProxmox
Backup agent locationWindows with ESXi accessLocal host / cluster nodeWindows with API access
Backing up changesCBTRCT on supported systemsIncremental backup
Selecting individual VM disksSupportedCheck the plan configurationAll attached disks
VM or item recoverySupported, depending on recovery methodSupported, depending on recovery methodSupported in current documentation
Encryption and schedulingSupportedSupportedSupported
Synthetic full backupDepends on plan and storageDepends on plan and storageFrom 8.6.5, with supported storage
Less data to transfer

Only part of the data changed?
Back up the changes.

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.

CBTChanged Block Tracking
Synthetic full backupBuild a full backup from existing backup data on supported storage
Move the slider.
See exactly what gets transferred.
How CBT works: full guide in Hebrew
Your disk, block by blockInteractive illustration

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 small distinction. A major difference.

A snapshot is a useful tool.
A backup is a separate copy.

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.

Snapshot

A recovery point within your production environment, dependent on source resources.

Virtual machineSnapshot

Same storage environment

Independent backup

A copy stored outside the source environment, with recovery points.

Virtual machineSeparate copy

Separation reduces dependence on the source

Start with a clear plan

A solid backup plan.
Step by step.

From critical machines to email alerts, these are the decisions that shape your backup plan.

BackupONE · VM BackupProcess illustration

What would you like to back up?

Select the machines that matter to your business.

ERP-SERVER✓ Selected
FILES-SERVER✓ Selected
TEST-SERVERNot selected

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

The moment you prepare for

Need to get back to work?
Start with a recovery point.

Choose what to restore, from which point and to which destination. Then verify that your data and applications are in the required state.

Backup is the beginning.
Recovery is the test.

Bring back the entire VM.

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.

Illustration only · Sample data

Which recovery point?

Sample ERP virtual machine
01Select backup
02Restore to host
03Verify the result

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.

A new VM or an existing destination

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 process

A physical server can return as a VM

A 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 recovery

System backup to vSphere

Another 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
An IT specialist with a tablet and a colleague reviewing the server environment
A clear plan for your team.Verify it in advance.
Habits that make a difference

Back up properly.
Test the route back.

01

Keep copies separate

A backup stored only on the source server shares the same point of failure. Plan an additional copy in a separate location.

02

Protect the backup itself

Enable encryption and store recovery credentials securely. Object Lock can add protection where supported by the edition and storage destination.

03

Test recovery

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.

3Data copies
The original and two backups
2Media types
Reduce shared dependencies
1Off-site copy
Separate from the source
VM backup best practices
Good questions

A few questions
before you start.

The details matter when adapting backup to your environment.

Does every VM need its own agent?

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.

Can I recover just one file?

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.

Is Proxmox Community Edition included in the service?

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

Is instant recovery guaranteed?

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.

How long should I keep recovery points?

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.

How do we know the backup fits our business?

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? נכיר את הסביבה שלכם ונתכנן גיבוי ושחזור שמתאימים לעסק. כדי שברגע האמת תהיה תכנית, ולא רק מישהו שיגיד ״ניסיתם לכבות ולהדליק?״