> Expert > Backup and Restore Agents > Virtualization > Virtual Server Agent > Microsoft Hyper-V > Configuration (Microsoft Hyper-V) > Client Configuration (Microsoft Hyper-V)

Creating a Virtualization Client (Microsoft Hyper-V)

Create a new virtualization client to manage backup and restore operations for virtual machines on a standalone Hyper-V server or a Hyper-V cluster. If you have multiple clusters or multiple standalone servers, create a virtualization client for each one.

To perform backup operations, each virtualization client can include multiple proxies where the Virtual Server Agent is installed. The virtualization client also enables proxy teaming, enabling proxy failovers for fault tolerant backups. Using multiple proxies for each virtualization client makes it possible to perform backups for a large number of virtual machines in a limited backup window.

Before You Begin

Complete the following requirements:

Obtain the user credentials to access the Hyper-V server from your Hyper-V administrator. The user must be part of the following administrator groups on the Hyper-V host:

  • Microsoft Hyper-V Server, versions 2016, 2019, and 2022

  • Local Administrators group (for Hyper-V Server 2008 R2 and Hyper-V Server 2016)

  • Any user that are part of Hyper-V Administrators group (for Hyper-V Server 2012 and 2012 R2)

    For a Hyper-V cluster, the user account must have full Cluster Permissions (Read and Full Control).

Procedure

  1. From the CommCell Browser, right-click the Client Computers node and click New Client > Virtualization > Microsoft Hyper-V.

    The Create Microsoft Hyper-V Client dialog box is displayed.

  2. In the Client Name box, enter a unique client name to describe the virtualization client.

    Note

    If you are using the host name of an existing client, the virtualization instance will be generated with _1 added to the end of the client name.

  3. To provide access to the Hyper-V client server, choose to do one of the following:

    • Manually enter user credentials

      In the Username and Password boxes, enter the user credentials to provide administrative access to access the Hyper-V server.

    • Use saved credential

      Select the Use saved credential check box, and then select a credential from the list of those available.

      The credentials listed are applicable to this client server.

      Note

      To create a new credential (with Windows account type), to the right of Credentials, click Create new. Enter the name of the new credential and the user name and password to provide administrative access to the client server. For more information, see Credential Manager.

  4. From the Storage Policy list, select a storage policy to associate with the virtualization client.

    The storage policy you select is also associated with the default subclient that is created automatically for the virtualization client.

  5. Click Add to identify one or more Hyper-V client nodes.

  6. In the Select Clients / Client Groups dialog box, choose Hyper-V servers to act as VSA proxies.

    After adding a virtualization client in V11, you can only specify VSA proxies that are also V11.

  7. Only proxies that match the type of the virtualization client are displayed.

    1. In the Exclude list, select the Hyper-V server with the Virtual Server Agent installed. If using a Hyper-V cluster setup, you can select one or more hyper-v nodes in the cluster with the Virtual Server Agent installed.

      The list displays all the Hyper-V servers that have the Virtual Server Agent installed and all the client groups. When you select a client group, ensure that at least one client in the group is a Hyper-V server with the Virtual Server Agent installed.

      The first node acts as a coordinator that allocates jobs to other proxy nodes.

    2. Click Include and then click OK.

  8. Click OK to create the virtualization client.

What to Do Next

By default, the default subclient backs up all the virtual machines in the standalone Hyper-V server or Hyper-V cluster. To change this behavior, see Adding a User-Defined Subclient.

Loading...