# Planning ## General information Using **Xopero ONE**, you can protect **Hyper-V** environments with native support for virtual machine backups, as well as file-level and image-level backups of the physical **Hyper-V** host. {% hint style="info" %} You can protect virtual machines using the **Hyper-V** backup type, while the **Hyper-V** host itself can be secured with file-level or image-level backups. {% endhint %} *** ## Backup overview The performance of the Hyper-V host is a key factor, as it determines how many virtual machines can be secured simultaneously. You can create backup for all machines on the host and automatically include any new machines created in the future. In the backup plan, under **Advanced settings** in the **Task balancing** tab, you can specify how many virtual machines should be backed up simultaneously. Alternatively, you can back them up individually with breaks in between. When protecting virtual machines, **Xopero ONE** uses the **RCT** (**Replica Change Tracking**) function to detect changes in virtual machine disk blocks, enabling much faster backups. Alternatively, you can choose to use the classic, slower method. You can configure the backup to bypass virtual machine disks that cannot be included in the system snapshot. This ensures the backup proceeds without those disks when snapshot inclusion isn't possible. *** ## Application-aware snapshots Backup of **Hyper-V** virtual machines is based on system snapshots. Different levels of support are available, but the goal is always to create **application-aware snapshots**, as they provide the highest consistency. With the **application-aware** option, **Hyper-V** also creates file-system consistent snapshots. For this reason, it is recommended to keep the **application-aware** option enabled, especially when protecting various **Linux** distributions. *** ## Useful links and items {% embed url="" %} {% embed url="" %}