Veeam Backup & Replication 9.5 Update 4
User Guide for Microsoft Hyper-V
Related documents

On-Host Backup

During on-host backup, VM data is processed on the source Microsoft Hyper-V host where VMs that you want to back up or replicate reside. All processing operations are performed directly on the source host that performs the role of the backup proxy. For this reason, on-host backup may result in high CPU usage and network overhead on the host system.

On-Host Backup Note:

The procedure below describes the backup process for Microsoft Hyper-V Server 2012 R2 and earlier. For more information about backup of VMs registered on Microsoft Hyper-V 2016 and later versions, see Online Backup and Crash-Consistent Backup.

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

  1. Veeam Backup & Replication triggers a snapshot of the necessary volume.
  2. The Veeam Data Mover on the host uses the created volume snapshot to retrieve VM data; it processes the VM data and copies it to the destination.
  3. After the backup process is complete, the volume snapshot is deleted.

On-Host Backup 

Assigning Role of On-Host Backup Proxy in CSV

The role of the backup proxy is assigned to a Microsoft Hyper-V host in CSV by the following rules:

Related Topics

This Document Help Center
User Guide for VMware vSphereUser Guide for Microsoft Hyper-VEnterprise Manager User GuideVeeam Cloud Connect GuideVeeam Agent Management GuideVeeam Explorers User GuideBackup and Restore of SQL Server DatabasesVeeam Plug-ins for Enterprise ApplicationsPowerShell ReferenceVeeam Explorers PowerShell ReferenceRESTful API ReferenceRequired Permissions ReferenceQuick Start Guide for VMware vSphereQuick Start Guide for Microsoft Hyper-VVeeam Backup for AWS DocumentationVeeam Availability for Nutanix AHV DocumentationVeeam Backup for Microsoft Office 365 DocumentationVeeam ONE DocumentationVeeam Agent for Windows DocumentationVeeam Agent for Linux DocumentationVeeam Management Pack Documentation
I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.