How to add Microsoft Hyper-V Standalone Servers to Veeam Backup and Replication v12

Veeam Backup & Replication allows you to build a scalable backup infrastructure for many environments. Physical and virtual machines can be added to the backup infrastructure and assigned different roles. Veeam Backup and Replication components can coexist on the same machine.

The Backup Infrastructure can be expanded with the following types of servers and hosts:

Microsoft Hyper-V Standalone Servers
Microsoft Hyper-V Cluster Servers
Microsoft SMB3 Servers
Microsoft Windows Servers
Linux Server

You must add the Microsoft Hyper-V standalone hosts you plan to use as source and target for backup, replication and other activities.

1. Log in to the Veeam Backup and replication manager server.

2. Open the Veeam Backup & Replication Console, and click Connect.

3. On the Home page, select Inventory.

4. On the Inventory page, select Virtual Infrastructure and click Add Server.

5. On the Add Server page, select Microsoft Hyper-V.

6. Enter the Microsoft Hyper-V server’s full DNS name or IP address on the Name page.

7. Give a brief description in the Description field for future reference and click Next.

8. Select Microsoft Hyper-V server (standalone) on the Type page and click Next.

9. Select an account from the Credentials drop-down list on the Credentials page or click Add on the right to add the credentials.

10. On the Credentials page, enter a user name in the Username field. You can also click Browse to select an existing user account.

11. Enter the password In the Password field.

12. Give a brief description in the Description field for future reference and click OK.

13. On the Credentials page, click Ports.

14. If necessary, change the network ports used by Veeam Backup & Replication components on the Network Settings page.

15. Configure connection settings for file copy operations in the Network Settings window’s Data transfer options section. Provide a set of ports for transmission channels between the source and target hosts (one port per task).

16. Select the Run server on this side checkbox in the Preferred TCP connection role section. The outside client cannot connect to the server on the NAT network in the NAT scenario. As a result, services that require external connection initiation may be disrupted.

17. Click OK.

18. Click Next on the Credentials page.

19. If you add a standalone Microsoft Hyper-V host on the Review page, specify the number of tasks the Microsoft Hyper-V host must handle concurrently in the Max concurrent tasks field.

20. Click Apply.