Off-Host Backup

In the off-host backup mode, backup processing is shifted from the source Microsoft Hyper-V host to a dedicated machine — an off-host backup proxy.

The off-host backup proxy acts as a “data mover”. Veeam Data Mover running on the off-host backup proxy retrieves VM data from the source volume, processes it and transfers data to the destination. This type of backup does not impose a load on the source host. As resource-intensive data processing operations are performed on the off-host backup proxy, production hosts remain unaffected.

To perform off-host backup, Veeam Backup & Replication uses transportable shadow copies. The transportable shadow copy technology lets the backup application create a snapshot of a data volume on which VM disks are located, and import, or mount, this snapshot onto another server in the same subsystem (SAN) for backup and other purposes. The transport process is accomplished in a few minutes, regardless of the amount of the data. The process is performed at the SAN storage layer, so it does not impact host CPU usage or network performance. For more information about transportable shadow copies, see Microsoft Docs.

To perform off-host backup, the backup infrastructure must meet the following requirements:

  • You must configure an off-host backup proxy. For more information, see Off-Host Backup Proxy.
  • In the properties of a backup or replication job, you must select the off-host backup method and off-host backup proxy that you want to use. If necessary, you can point the job to a specific off-host backup proxy. For more information, see Configuring Advanced Options for Off-Host Backup Proxies.

The off-host backup process is performed in the following way:

  1. Veeam Backup & Replication triggers a snapshot of the necessary volume on the Microsoft Hyper-V host.
  2. The created snapshot is detached from the host and mounted to the off-host backup proxy.
  3. Veeam Data Mover, running on the off-host backup proxy, uses the mounted volume snapshot as a data source. It retrieves VM data from the volume snapshot, processes it and transports data to the destination.
  4. After the backup process is complete, the snapshot is dismounted from the off-host backup proxy and deleted on the storage system.


If you plan to perform an off-host backup for a Microsoft Hyper-V cluster with CSV, make sure you deploy an off-host backup proxy on a host that is NOT a part of a Hyper-V cluster.
When a volume snapshot is created, this snapshot has the same LUN signature as the original volume. Microsoft Cluster Services do not support LUNs with duplicate signatures and partition layout. For this reason, volume snapshots must be transported to an off-host backup proxy outside the cluster. If the off-host backup proxy is deployed on a node of a Microsoft Hyper-V cluster, a duplicate LUN signature will be generated, and the cluster will fail during backup or replication.

Off-Host Backup 

Helpful Resources

The VSS hardware provider for Dell PowerVault can be found on the Resource CD.

The VSS hardware provider is a part of Host Integration Tool (HIT/Microsoft).

To get detailed information, contact your storage vendor.

Related Topics

Page updated 2/20/2024

Page content applies to build