Skip to main content

How can we help you?

Druva Documentation

Install the agent and register a Hyper-V host

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite


Before you can backup your virtual machines, you have to register the Hyper-V host on which you create and manage virtual machines. During registration, Druva Phoenix generates an activation token that activates the Phoenix agent installed on your host. Activation ensures that Phoenix agent establishes a persistent connection with Druva Cloud and registers your host with Druva Phoenix. After your host is registered, backup is enabled for the host on which the agent is installed. The Phoenix agent:

  • Scans your host and requests the VSS service for the virtual machine snapshot
  • Backs up the snapshot on the cloud
  • Restores data from the cloud when you request it

For an overview of configuration steps, see:

This article contains the following sections:

Step 1: Download the agent and generate activation token

  1. Log in to Phoenix Management Console.
  2. On the menu bar, click the drop-down next to All Organizations and select the Organization. 
  3. On the menu bar, click Protect > Hyper-V
  4. Click Register Hyper-V Host.
  5. On the Register New Hyper-V Host page, click Check prerequisites and ensure that you review the requirements before configuring Hyper-V hosts for backup.
  6. Under Download and install agent on the host, do one of the following:
    • If you have not yet downloaded the Phoenix agent installer, click Download. The agent download starts on the same browser page. 
    • If the Phoenix agent has already been downloaded, proceed to the Activate Host for Backup section.
  7. Under the Activation Token field, you can select a pre-existing activation token from the drop-down. An activation token can be used to activate up to 25 servers and expires in 7 days. If this token has expired, click Generate New Token. In the Generate Token dialog box, enter the following details, and then click Generate
    Field Description
    Token Label

    A short description of the activation token.

    Note: You cannot leave this field empty.

    This token can activate

    The number of hosts that the activation token can activate.

    The default value is 25.

    The token expires in

    The number of days after which the activation token expires.

    The default value is 7. 

  8. In the Generate Token window that follows, you can copy the generated token by clicking the Copy Token icon. Click Done.
    Copy token.png

Step 2: Install the agent

Before you begin, ensure that:

  • You are logged in as an administrator to the host.
  • Your host matches the requirements listed in the support matrix
  • You have downloaded the Phoenix agent installer on your host. The installer is available on the Druva downloads page. You can also download the installer from the Phoenix Management Console at the time of registering hosts. 

Perform the following steps to install the agent:

  1. Copy the downloaded Phoenix agent installer to the host on which you want to install it.
  2. Double-click the Phoenix agent installer. The installation wizard appears.
  3. Accept the license agreement and click Next
  4. Use the local system account for installing the agent on the Hyper-V host. 
  5. In the Install location box, enter or select the full path to the installation home directory. 
  6. Click Install.
  7. After the installation completes, click Finish.

Command-line install

From the command prompt, run the following command:

msiexec /i <path to Phoenix msi> /qn /quiet /log <path to log file>

Configure web-proxy (optional) 

The Phoenix agent connects to the Druva Cloud through the internet. If your network infrastructure uses a web-proxy, configure the Phoenix agent to use the web-proxy to establish a connection with the Druva Cloud. 

Before you begin, ensure that the Phoenix agent is running before you start proxy settings.

To configure the web-proxy:

  1. Open the command line interface window.
  2. Change the directory path to the location on the system on which the Phoenix agent is installed.
    Windows default: C:\Program Files\Druva\Phoenix Agent
  3. On command prompt, run the following command:
    PhoenixHyperVControl.exe set_proxy_details -t proxy_type -i proxy_IP:port -u proxy_user -p proxy_password
    Field Description
    Proxy_type Druva supports the following proxy types:
    • http
    • socks4
    • socks5
    Proxy_IP Valid IP of the proxy server
    Port Respective proxy port number
    Proxy_user Valid proxy username. Enter * for an unauthenticated proxy.
    Proxy_password Valid proxy password. Enter * for an unauthenticated proxy.

Note: Druva only supports basic authentication with web-proxy.

The web-proxy is configured successfully if you see the message Proxy details updated successfully on the terminal. Do not use quotes for proxy_IP, proxy_user or proxy_password. All the parameters must be present, if any input parameter is missing or not in prescribed order, then the utility will fail.

Additional information

  1. The Threat Management Gateway (TMG) drops idle connections after defined timeout duration, due to which the connection between the Phoenix agent and the Druva Cloud breaks.  Druva recommends that the connection timeout value is set to 5 minutes in the TMG application to avoid this problem.
  1. The configuration file path for the Phoenix agent is C:\ProgramData\Phoenix\Phoenix.cfg.
  2. Manually remove following proxy entries from Phoenix.cfg file if you want to remove proxy setting after successfully setting it up.

     After deleting the entries, set USE_PROXY = False in the Phoenix.cfg file. 

  1. If the proxy-details setting fails, ping the proxy-server IP from the same machine and check for proxy_user and proxy_password.

Step 3: Activate the Phoenix agent

Activate the agent using the Windows command line

  1. Open the command-line prompt with Admin privilege, and change the directory to the agent installation directory.

    For example, Phoenix agent is installed on C:\Program Files\Druva\Phoenix Agent.
    To change the directory in CLI, run: cd “C:\Program Files\Druva\Phoenix Agent”

  2. After changing the directory, run the following commands to activate the agent:

    For Druva Cloud:

    PhoenixHyperVControl.exe activate <activation_token> --type <scvmm/cluster/standalone> --scvmm_fqdn <scvmm FQDN> --user <scvmm/cluster username> --password <scvmm/cluster password>

    For GovCloud:

    PhoenixHyperVControl.exe activate govcloud <activation_token> --type <scvmm/cluster/standalone> --scvmm_fqdn <scvmm FQDN> --user <scvmm/cluster username> --password <scvmm/cluster password>
  • Replace <activation_token> with the activation token that Druva Phoenix generated at the time of registering the host.
  • For --type, select one of the following parameters based on your setup
    • scvmm
    • cluster
    • standalone
  • Provide IP address or Fully Qualified Domain name for <scvmm FQDN>
  • If the Hyper-V host uses SCVMM, replace <scvmm username> and <scvmm password>
     with username and password respectively. 
    If you are registering the Hyper-V host as a cluster, replace <cluster username> and <cluster password> with domain username and password respectively. Ensure that the domain user has access permissions on all the Hyper-V hosts within that cluster.
  • For example, if you are registering an SCVMM based host

    PhoenixHyperVControl.exe activate 111111AAAAAA --type scvmm --scvmm_fqdn --user admin --password examplepasswordforscvmm
  • If you are registering a clustered host:
    PhoenixHyperVControl.exe activate 111111AAAAAA --type cluster --user exampledomain\admin --password examplepasswordfordomainuser
  • If you are registering a standalone host:
    PhoenixHyperVControl.exe activate 111111AAAAAA --type standalone
  • If you are registering for Gov Cloud, add the govcloud parameter. For example, in case of a standalone host:
    PhoenixHyperVControl.exe activate govcloud 111111AAAAAA --type standalone
  • The --scvmm_fqdn parameter is applicable for System Center Virtual Machine Manager based host only. It is not applicable for a standalone host or a host in a cluster.
  • The --user and --password parameters are not required for standalone hosts.
  • In place of the --type, --user, --password, and --scvmm_fqdn parameters, you can use -e, -u, -p, and -f  respectively. 
  • If you move a host from one cluster to another after registration, the host appears as disconnected in the Phoenix Management Console.
  • By default, the server is registered using its Fully Qualified Domain Name (FQDN). In addition, you can use the --ServerName  or -d parameter to register your host with a name. The server name is not case-sensitive. You cannot have one server registered as "ABC" and another as "abc". Druva Phoenix will display the error message "Server display name already exists. Cannot register the server with same display name". You can add the -d parameter to register the server with a different name. 
  • You can upgrade Phoenix agents to their latest available version. For more information, see Upgrade the agent.
  • If you are using SCVMM for managing virtual machines on Windows Server 2008 and Windows Server 2008 R2 hosts:
    • When you activate the Phoenix agent, select the type as standalone or cluster (based on your setup). Do not select the type as scvmm to register the hosts through SCVMM.
    • Phoenix does not support registration of the Microsoft Windows Server 2008 and Microsoft Windows Server 2008 R2 hosts through SCVMM.

If you want to update the credentials later:

PhoenixHyperVControl.exe set_credential --type <scvmm/cluster> --scvmm_fqdn <scvmm FQDN> --user <scvmm/cluster username> --password <scvmm/cluster password>

For example, 

PhoenixHyperVControl.exe set_credential --type scvmm --scvmm_fqdn= --user=exampledomain\user --password=Ex@mpleP@$$w0rd

Note: Do not use the following characters in the command:

  • Double quotes "
  • Single quotes '
  • Double back-slash \\


Note: The File level restore requires an additional proxy. For more information, see File-level restore (FLR) on Hyper-V virtual machines.

Next steps

After the server is registered, configure virtual machines for backup

For information on how to configure Druva Phoenix so that it can work with third-party VSS providers, see How do I configure Druva Phoenix to use third party VSS providers?