# Creating a backup plan

## General information

One of the key features of **Xopero ONE** software is **VMware** backup. The system enables you to back up all or selected virtual machines hosted on your **ESXi** or **vCenter** server. This article focuses on creating a **VMware** backup plan.

***

## Creating a backup plan

{% stepper %}
{% step %}
Log in to [**XMS**](#user-content-fn-1)[^1], go to the **Backup** tab (**Plans** > **Backup**) and click the **+ Add plan** button in the top toolbar.

<figure><img src="/files/4vnONYo4CncYWJyACJ9Z" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select **VMware** from the platforms list.

<figure><img src="/files/0wGTqzUwGy0AYGGXKx0m" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Define the name of the backup plan.
{% endstep %}

{% step %}
Select one of the available **ESXi** or **vCenter** servers (from those already connected to **Xopero ONE**) and choose which virtual machines you want to protect. You can select **Protect all** to include all VMs from the chosen server, or **Select VMs** to manually add only specific virtual machines.

<figure><img src="/files/qnOVaEmOGvdV3ZGrexnu" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click the **Edit** button next to the **VMware backup options** section to configure the following settings:

<figure><img src="/files/U4HDFLsP8rPtyuVgivhn" alt=""><figcaption></figcaption></figure>

1. **Application aware** — a **VSS**-based feature that ensures a consistent backup of the virtual machine and its applications (for example, **Windows Server** systems running **Microsoft SQL Server**, **Microsoft Exchange**, or **Microsoft Active Directory**). In **Xopero ONE**, you can enable **application-aware backup** on supported guest operating systems (recommended). You can also choose to continue the backup in case of application errors—if this option is enabled, the backup process will proceed even if the **application-aware** feature encounters an error.

<figure><img src="/files/nKDHJXeVXszt8ET2uWJ5" alt=""><figcaption></figcaption></figure>

2. **Changes processing (CBT)** — a feature that lets you configure how differential and incremental backups are performed. You can choose between the following options:
   1. **VMware CBT** (recommended) — a **VMkernel** feature that tracks changes to the storage blocks of virtual machines over time. For **VMware CBT**, there are two additional settings: **Enable CBT in VMware** for all VMs included in the backup, and **Reset CBT for every full copy** to prevent any issues related to **CBT**.
   2. **Xopero ONE classic method** — a less efficient but useful option when **VMware CBT** fails. This method compares data block by block to identify changes between the previous and current backup.&#x20;

<figure><img src="/files/Rjufadb3SG1WmZ4a1JQO" alt=""><figcaption></figcaption></figure>

3. **Virtual machine state** — an optional feature that lets you specify the VM states in which the backup should be performed. If a virtual machine is in a different state than the one selected, it will not be included in the backup process.
4. **Transport method** — defines how virtual machines are transferred between **VMware** and the **backup worker**. There are four options available:
   1. **Automatic (recommended)** — **Xopero ONE** will automatically determine the best available transport method for each worker and apply it accordingly.
   2. **HotAdd** — available only for **virtual appliance workers** (see [this article](/xopero-one-en/backup-and-recovery/virtual-machines/vmware/integration/virtual-appliance.md) for more details). This method creates a snapshot and a linked clone of the target virtual machine. The disk is then attached to the **worker**, which reads the linked clone’s virtual disks for backup.
   3. **SAN** — this mode requires the backup server to have access to the **SAN** storage containing the virtual disks. A **SAN backup worker** must be a physical machine. In this mode, data is read directly from the **VMware LUN** storage where the virtual disks are located.
   4. **LAN** — also called **NBD**/**NBDSSL**. In this mode, the **ESXi** host reads data from the storage and sends it over the network to the worker. This method is typically used when no other transport option is available.

<figure><img src="/files/IT1jASJTUrDBtHvgh4ij" alt=""><figcaption></figcaption></figure>

5. **Skip SWAP and empty blocks** — **Xopero ONE** allows you to reduce backup size using two additional options:
   1. **Skip SWAP files, and partitions** — when this option is enabled, **Xopero ONE** will skip swap partitions and files. These function as virtual memory, storing temporary data that is not currently used by RAM.
   2. **Skip empty blocks** — when this option is enabled, **Xopero ONE** will skip empty blocks that do not need to be backed up, reducing the overall backup size.

<figure><img src="/files/WUQhNYGmP5jgaz8GGe1Z" alt=""><figcaption></figcaption></figure>

6. **Disk consolidation:** when this option is enabled, **Xopero ONE** forces consolidation of the source machine's disks on the **VMware** side before taking a snapshot.&#x20;

<figure><img src="/files/b9rEl2SzailDxh0MuqWQ" alt=""><figcaption></figcaption></figure>

7. **Default worker** — device directly responsible for backing up your virtual machines. You can have multiple workers and assign different workers to each backup plan. A worker can be either a physical or virtual machine.

<figure><img src="/files/Px3QhbYdHxSDEwxUdwXv" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Note that using transport methods like **HotAdd** requires a **virtual appliance**.
{% endhint %}

{% hint style="danger" %}
Devices running on **macOS** cannot be used as **worker** devices in VMware backup plans in Xopero ONE.
{% endhint %}
{% endstep %}

{% step %}
Specify the backup location by choosing from the available storage options within your service.
{% endstep %}

{% step %}
Configure the [**Scheduler & data retention** settings](/xopero-one-en/management/scheduler-and-retention.md) by defining when backups should run and which types of backup copies to use.

{% hint style="danger" %}
Set the retention policy to determine how long backups are stored — any copies exceeding this period <mark style="color:$danger;">**will be automatically deleted**</mark>.
{% endhint %}
{% endstep %}

{% step %}
Go to the **Advanced settings** section to customize additional options, including encryption, compression levels, and deduplication. These settings provide greater flexibility and help optimize the backup process.
{% endstep %}

{% step %}
After completing the configuration, click the **Save** button. The protection plan will then automatically begin protecting your **VMware** virtual machines according to the schedule you defined.
{% endstep %}
{% endstepper %}

***

## Useful links and items

{% content-ref url="/pages/7HrIOJELj5Aypl0FKmVD" %}
[Adding VMware server to Xopero ONE](/xopero-one-en/backup-and-recovery/virtual-machines/vmware/integration/adding-vmware-server-to-xopero-one.md)
{% endcontent-ref %}

[^1]: Xopero ONE Management Service


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://helpcenter.xopero.com/xopero-one-en/backup-and-recovery/virtual-machines/vmware/backup/creating-a-backup-plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.