Before You Begin

Before you add a Microsoft Hyper-V server to the backup infrastructure, check the following prerequisites:

Check permissions required to add the server. For more information, see Permissions.
Make sure that you do not add to the backup infrastructure Hyper-V hosts or clusters managed by an SCVMM server if this SCVMM server is already added to the backup infrastructure.

File and printer sharing must be enabled in network connection settings of the added Microsoft Hyper-V host. Otherwise, Veeam Backup & Replication will fail to deploy required components.
Make sure that the NETBIOS name of the Microsoft Hyper-V Server is successfully resolved.
The option to use Veeam Deployment Kit for certificate-based authentication is not available for Hyper-V clusters. Credential-based authentication is required for communication with the Hyper-V cluster objects. For more information, see Using Veeam Deployment Kit.
[For Linux-based backup servers] Both the Hyper-V nodes and the backup server must be joined to the same Active Directory domain. If they are not joined to the same Active Directory domain, additional manual configuration of the krb5.conf file is required. For more information, see Performing Maintenance Tasks.
Linux-based backup servers do not support Hyper-V workgroup clusters. This configuration is available only for Microsoft Windows-based backup servers.

If you get the "Invalid Credentials" error when adding a Hyper-V host using a local account, see this Veeam KB article.
Veeam Backup & Replication ignores the SCVMM maintenance mode on Hyper-V hosts and Hyper-V cluster nodes. That is, Veeam Backup & Replication continues all data protection activities and allows launching new ones.