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, Phoenix generates an activation token that activates Phoenix agents installed on your host. Activation ensures that Phoenix agent establishes a persistent connection with Phoenix Cloud and registers your host with 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:
- Download the agent and generate activation token
- Install the agent
- Activate the agent
Step 1: Download the agent and generate activation token
- Log on to Phoenix Management Console.
- On the menu bar, click All Organizations, and select the required organization from the drop-down list.
- On the menu bar, click Protect > Hyper-V.
- Click Register New Setup.
- On the Register Server page, under Install Druva Phoenix Agent, do one of the following:
- If you have not yet downloaded the Phoenix Agent installer, click the download link, and click Next.
- If you downloaded Phoenix Agent, skip this step, and click Next.
- Under Generate Activation Token, provide the following details, and click Next.
Field Description Token Description
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.
- Under Server Activation, click Copy and save the activation token in a text file.
- Click Finish.
Step 2: Install the agent
Before you begin, ensure:
- 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 installer. The installation wizard opens.
- In the first step, 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, type 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)
Phoenix agent connects to the Phoenix Cloud through the internet. If your network infrastructure uses a web-proxy, configure the Phoenix agent to use web-proxy to establish a connection with the Phoenix Cloud.
Before you begin, ensure that Phoenix client 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 your system, where 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. Proxy_password Valid proxy password.
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.
Note: 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 TMG drops IDLE connections after defined timeout duration, due to which agent retries aggressively with the server.
Note: In TMG application, it is recommended to set connection timeout value to 5 minutes.
- The configuration file path for Phoenix agent and Cache Server are as follows:
- If you want to remove proxy setting after successfully setting it up, then you must manually remove following proxy entries from Phoenix.cfg.
Note: After deleting the above listed entries, set USE_PROXY = False in same 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 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 directory in CLI, you run: cd “C:\Program Files\Druva\Phoenix Agent”
After changing the directory, run the following commands to activate the agent :
For Phoenix 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 Phoenix generated at the time of registering the host.
- For --type, select one of <scvmm/cluster/standalone> 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 Hyper-V hosts within that cluster.
For example,PhoenixHyperVControl.exe activate 111111AAAAAA --type scvmm --scvmm_fqdn examplehyperv.fqdn.yourorg.com --user admin --password examplepasswordforscvmm
- --scvmm_fqdn 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.
- --user and --password parameters are not required for standalone hosts.
- 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 parameter to register your server with a name. The Server Name is not case sensitive. You cannot have one server registered as "ABC" and another as "abc". 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 your hosts through SCVMM.
- Phoenix does not support registration of 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 quotes (" or ') in the command.
After the server is registered, configure virtual machines for backup.
For information on how to configure Phoenix so that it can work with third party VSS providers, see How do I configure Phoenix to use third party VSS providers?