Re-register a Hyper-V host if:
- You initially registered it as a standalone host, and you want to re-register the host as a part of a cluster
- You initially registered it as a standalone host, and you want to re-register a host that is managed using System Center Virtual Machine Manager (SCVMM)
- You initially registered the host as a part of the cluster, and you want to re-register a host that is managed using SCVMM
- You refreshed the hardware of the host and the host is disconnected from the Druva Cloud after the hardware refresh
- Your host is disconnected from the Druva Cloud if the Phoenix.cfg file gets deleted
You can use Druva Phoenix to re-register a Hyper-V host so that:
- It is not registered as a new host with Druva Phoenix.
- The Phoenix agent creates successive snapshots of the virtual machines running on the host.
- The Druva Cloud does not store the snapshots as snapshots from a different host.
To re-register a host, download the Phoenix agent from the Phoenix Management Console, and install and activate the Phoenix agent once again on the host. Re-registration of a host requires three steps:
- Download the Phoenix agent and generate an activation token
- Install the Phoenix agent
- Activate the Phoenix agent
Note: If you plan to change the management type of the host virtual machine, such as SCVMM, Standalone, or Cluster, the state of the host virtual machine on the Druva Cloud must be in sync with the state of the virtual machine in your infrastructure. Before the re-registration of the host, ensure that the host is connected to the Druva Cloud and the virtual machine list is refreshed. If the host is disconnected, you must first re-register the host with the same management type, refresh the list of virtual machines, and then re-register to change the management type.
Step 1: Download the Phoenix agent and generate the activation token
To re-register a host, perform the following steps:
- Log on to Phoenix Management Console.
- On the menu bar, click the drop-down next to All Organizations and select the Organization.
- On the menu bar, click Protect > Hyper-V.
- In the left navigation pane, click Hosts. On the Hosts page, select the host that you want to re-register.
Note: You can apply filters based on VM, Host, Cluster, or SCVMM.
- Click more options and then click Re-register.
- Click Proceed on the Re-register Hyper-V Host dialog.
- On the Re-register Hyper-V Host page, click Check prerequisites and ensure that you review the requirements before configuring Hyper-V hosts for backup.
- 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.
- Under the Activation Token field, click the Copy Token icon to copy the activation token and save it in a text file.
Ensure that you use this activation token for the correct host. If you use this re-registration activation token to re-register a different host, backup jobs will fail for virtual machines running on the other host as well for the virtual machines running on the host you originally wanted to re-register. In addition, on the Hosts tab of the Hyper-V page, details of the other host become identical to the host you originally wanted to re-register.
- Click Done.
Step 2: Install the Phoenix 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:
- Copy the downloaded Phoenix agent installer to the host on which you want to install it.
- Double-click the Phoenix agent installer. The installation wizard appears.
- Accept the license agreement and click Next.
- Use the local system account for installing the agent on the Hyper-V host.
- In the Install location box, enter or select the full path to the installation home directory.
- Click Install.
- After the installation completes, click Finish.
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:
- Open the command line interface window.
- 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
- 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:
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.
- 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.
- The configuration file path for the Phoenix agent is C:\ProgramData\Phoenix\Phoenix.cfg.
- 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.
- 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
After you install the Phoenix agent, activate it on the Hyper-V host. To activate the Phoenix agent:
- 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”
- 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>
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
- 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 hostPhoenixHyperVControl.exe activate 111111AAAAAA --type scvmm --scvmm_fqdn examplehyperv.fqdn.yourorg.com --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>
PhoenixHyperVControl.exe set_credential --type scvmm --scvmm_fqdn=192.0.2.9 --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.