Skip to main content
druva_logo.pngDruva
|
Documentation

How can we help you?

 

Trending articles:
Druva Documentation

Common agent installation and activation

  1. Last updated
  2. Save as PDF
Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

 

Using the common Hybrid Workloads agent, you can install the agent and activate it for different workloads on a Windows or Linux server, thereby saving time for installing and activating the agent individually for each workload.

Common agent installation and activation on a Windows Server

With the common agent, you can protect File Servers, MS SQL, NAS, and Hyper-V workloads. 

Benefits

You can use this feature to:

  • Download only one common Hybrid Workloads agent to protect multiple workloads.
  • One-time installation of the Hybrid Workloads agent on the Windows Server.
  • Activate multiple workloads simultaneously using the common Agent Activation screen.

The following diagram depicts the steps to use the common agent. 

Infographic_phx-ready_new.png

Watch video 

Related Videos

 

The steps include the following:

Step 1: Download agent and generate activation token

You can protect different types of workloads using the common agent. For example, if you download the agent for File Servers, the same can be used to protect MS SQL, NAS, and Hyper-V workloads and vice-versa. The agent is also available for download on the Druva Downloads page. The steps to download an agent and generate an activation token are as follows:

  1. Log in to the Management Console.
  2. Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
  3. For each workload, select the following option:
    • Click Register New Server for File Servers and MS SQL Servers.
    • Click Add Proxy for NAS.
    • Click Register Hyper-V Host for Hyper-V. 
      The respective registration screens appear. 
  4. Under the Download and Install Agent on the Server section, in the Select OS drop-down, select Windows - 64 bit. 
    Note: 
    • You can click Check Pre-requisite to check the Hybrid Workloads agent prerequisites.
    • For Hyper-V and NAS, directly select the Windows Download option.
  5. Click Download.
    The agent download starts on the same browser page.
  6. Under the Activation Token section, if there aren't any existing tokens, a Default Activation Token is generated. This token is valid for 25 servers and for 7 days. 
    Note: If this token has expired, click Generate New Token. In the Generate Token dialog box, enter the required details, and click Generate. 
  7. Select the Copy Token icon. 
    The activation token is copied successfully. 

Step 2: Install and activate agent

Install the agent 

  1. Go to the location where you have downloaded the Hybrid Workloads agent installer.
  2. Double-click the Hybrid Workloads agent installer.
  3. Click Next. 
  4. Use a local system account to install the agent on the Windows server. 
    Note: Ensure that the available disk space is at least twice the size of the installer file.  
  5. Type or select the full path to the installation home directory in the Install location box. 
  6. Click Install.
  7. After the installation completes, click Finish.

Activate the agent

After installing the Hybrid Workloads agent on a Windows server; you must activate that Hybrid Workloads agent using the activation token that Management Console generated when registering servers. The following example shows the steps to activate the File Servers, MS SQL Servers, NAS, and Hyper-V using the Hybrid Workloads agent. 

Note: 

Procedure:

  1. Double-click the Hybrid Workloads Agent shortcut on the server where the agent needs to be activated. 
    The Hybrid Workloads Agent window is displayed.
    Activateagent.png
  2.  In the Hybrid Workloads Agent window, select Files & MS-SQL workload to activate. 
    The Agent Activation page for Files & MS-SQL is displayed.
    Fs_activatescreen.png
  3. Enter the following details:
Field  Description
Activation Token Paste the copied activation token.
Note: This is the token copied from the Register New Server dialog box. 
Server Name Enter a unique server name in the current Organization for each workload of the same type.
Note: The server name should not contain any special characters.

Note: If you are activating the Hybrid Workloads agent for Druva Public Cloud, do not select the GovCloud check box.

  1. Click Activate. 
    The File & MS-SQL agent is activated successfully.
    FS_activated.png
  2. In the Hybrid Workloads Agent window, click the Add Workload option and select NAS. 
    The Agent Activation page for NAS is displayed.
    NAS_activatescreen.png
  3. Enter the following details:
Field  Description
Activation Token Paste the copied activation token.
Note: This is the token copied from the Add NAS Proxy dialog box. 
Proxy Name Enter a unique proxy name in the current Organization for each workload of the same type.
Note: The proxy name should not contain any special characters.

Note: If you are activating the Hybrid Workloads agent for Druva Public Cloud, do not select the GovCloud check box.

  1. Click Activate. 
    The NAS agent is activated successfully.
    NAS_activated.png
  2.  In the Hybrid Workloads Agent window, click the Add Workload option and select Hyper-V. 
    The Agent Activation page for Hyper-V is displayed.
    Hyperv_activatescreen.png
  3. Enter the following details: 
    Field  Description
    Activation Token Paste the copied activation token.
    Note: This is the token copied from the Register New Hyper-V Host dialog box. 
    Register Host As Select the host type based on your setup. The available options are SCVMM, Cluster, Standalone. The default option is Standalone. 
    SCVMM FQDN Provide IP address or Fully Qualified Domain name.
    This field displays only when you select SCVMM as the host type in the Register Host As field. 
    Username Enter a valid user name. 
    This field displays only when you select SCVMM or Cluster as the host type in the Register Host As field. 
    Password Enter a valid password.
    This field displays only when you select SCVMM or Cluster as the host type in the Register Host As field. 
    Note: If you are activating the Hybrid Workloads agent for Druva Public Cloud, do not select the GovCloud check box.
  4. Click Activate. 
    The Hyper-V agent is activated successfully.
    Hyperv_activated.png

Step 3: Configure Web proxy using the user interface

Hybrid Workloads agent connects to the Druva Cloud through the internet. If your network infrastructure uses a Web proxy, configure the Hybrid Workloads agent to use Web proxy to establish a connection with the Druva Cloud. 
Before you begin
Ensure that the Hybrid Workloads agent service is running before starting proxy settings.

Procedure:

  1. Double-click the Hybrid Workloads Agent application. 
  2. In the Agent Activation window, select Configure Web Proxy.
    1. Select the My network infrastructure uses a Web proxy check box to enter the details.
      The Web Proxy options are displayed.
      Webproxy.png
    2. In the Proxy Type drop-down list, select one of the supported proxy types(http, socks4, socks5). The default selection is http. 
    3. In the Proxy Server IP Address field, enter a valid IP address of the proxy server.
    4. In the Proxy Port field, enter the respective port number.
    5. If your proxy requires authentication, select the Proxy server requires authentication check box and add relevant username and password in their respective fields.
  3. Click Save.
    The Web proxy is configured.
    Note: You can delete the Web proxy in the Windows file server once it is set up successfully by following the below procedure:
    1. Clear the My network infrastructure uses a Web proxy check box.
    2. Click Save.

Common agent installation and activation on a Linux Server

Using the common Hybrid Workloads agent, you can install the agent and activate it for your File Servers and NAS workloads on a Linux server based on your requirement, thereby saving time for installing and activating the agent individually for each workload. 
The steps include the following:

Step 1: Download and generate activation token

You can protect different types of workloads using the common agent. For example, if you download the agent for File Servers, the same can be used to protect NAS and vice-versa. The agent is also available for download on the Druva Downloads page. The steps to download an agent and generate an activation token are as follows:

  1. Log in to the Management Console.
  2. Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
  3. For each workload, select the following option:
    1. Click Register New Server for File Servers.
    2. Click Add Proxy for NAS.
      The respective registration screens appear. 
  4. Under the Download and Install Agent on the Server section, select Linux in the Select OS drop-down. 
    Note: 
    • You can click Check Pre-requisite to check the Hybrid Workloads agent prerequisites.
    • For NAS, directly select the Linux Download option.
  5. Click Download.
    The agent download starts on the same browser page.
  6. Under the Activation Token section, if there aren't any existing tokens, a Default Activation Token is generated. This token is valid for 25 servers and for 7 days. 
    Note: If this token has expired, click Generate New Token. In the Generate Token dialog box, enter the required details, and click Generate. 
  7. Select the Copy Token icon. 
    The activation token is copied successfully.

Step 2: Install and activate agent 

Perform the following steps to install the agent: 

  1. Go to the directory that contains the Hybrid Workloads agent installer.
  2. Run the following command: 
    dpkg -i <package_name>

    For example:
dpkg -i druva-phoenix-client-6.0.1-131748.amd64.deb
    or 
    rpm –ivh <package name>

    For example:
rpm –ivh druva-phoenix-client-6.0.1-131748.x86_64.rpm
    Note: Ensure that the available disk space is at least twice the size of the installer file.

Perform the following steps to activate the agent:

Note: If your network infrastructure uses a Web proxy, you must configure it before activation. For more information, see Configure Web proxy.
  1. On the Linux server, open the terminal.
  2. Paste the copied command for File Servers as explained below:
    1. Public Cloud 
      HybridWorkloadsAgent fs activate -t <token> -n <ServerName> 

      For example:
HybridWorkloadsAgent fs activate -t 32931-228-1762-591132241ce4fb2e14fca792cbf532f4a2359eb0bf1b96f82211373ebea7c23b -n WIN-RFE3
    2. GovCloud 
      HybridWorkloadsAgent fs activate -g -t <token> -n <ServerName>

      For example:
HybridWorkloadsAgent fs activate -g -t 32931-228-1762-591132241ce4fb2e14fca792cbf532f4a2359eb0bf1b96f82211373ebea7c23b -n WIN-RFE3
  3. Paste the copied command for NAS as explained below:
    1. Public Cloud 
      HybridWorkloadsAgent nas activate -t <token> -n <ProxyName>

      For example:
HybridWorkloadsAgent nas activate -t 52931-221-1762-591132241ce4fb2e14fca792cbf532f4a2359eb0bf1b96f8221343eb233c44a -n WIN-RTG3
    2. GovCloud 
      HybridWorkloadsAgent nas activate -g -t <token> -n <ProxyName>

      For example:
HybridWorkloadsAgent nas activate -g -t 52931-221-1762-591132241ce4fb2e14fca792cbf532f4a2359eb0bf1b96f8221343eb233c44a -n WIN-RTG3
      The agent is activated successfully.

 where,

  • <token> represents the activation token that Druva Phoenix generated at the time of registering server.
  • <ServerName> represents the tag to the server that you want to activate. You can tag a server during activation or after activation. For example, if you add the 'druva_file_server' tag to your server, you can search for the server on the Druva Phoenix portal using the 'druva_file_server' name. This is an optional argument. If you do not provide any value for this argument, the FQDN of the server is assigned as the default value for this attribute.
  • <ProxyName> represents the tag to the proxy that you want to activate.

Step 3: Configure Web proxy

Before you begin
Ensure that the Hybrid Workloads agent service is running before starting proxy settings.

Procedure

  1. Open the command line interface window.
  2. In the terminal, run the following command set the Web proxy: 
    HybridWorkloadsAgent web-proxy-config -s -t <proxy_type> -i <ProxyHost_IP>:port -u <Proxy_user> -p <Proxy_password>
  3. (Optional)You can use the following command to fetch the current proxy configuration: 
    HybridWorkloadsAgent web-proxy-config -g
    Field  Description
    Get_web-proxy
    (-g, --get)    		 Fetches the current Web proxy configuration for the agent.
    Set_web_proxy
    (-s, --set)    		 Sets the current Web proxy configuration for the agent.
    Proxy_type
    (-t, --proxy-type string)    		 Agent supports the following proxy types:
    • http
    • socks4
    • socks5
    Note: If you do not provide the type, http is applied by default.
    Proxy_IP
    (-i, --host string)    		 Valid IP or URL of proxy server.
    Port Respective proxy port number.
    Proxy_user
    (-u, --user string)    		 Valid proxy user name. 
    Proxy_password
    (-p, --pass string)    		 Valid proxy password.
    The Web proxy is configured successfully.
    Note: 
    • Do not use quotes for proxy_IP, proxy_user or proxy_password. 
    • In the terminal, run the following command in the Linux server to remove the Web proxy:
      HybridWorkloadsAgent web-proxy-config -r
      or
      HybridWorkloadsAgent web-proxy-config --remove