This article provides the following steps to set up Phoenix on your server:
- Install the agent on your server
- (Optional) Configure web proxy on Windows
- Generate activation token
- Activate the agent
Before you begin
Before you can set up Phoenix in your infrastructure, ensure that you have configured organizations and administrators. For more information, see Quick steps to set up Phoenix to back up databases.
Ensure that you read through the system requirements and prerequisites.
Step 1: Install the agent on your server
- Go to the location where you have downloaded the Phoenix Agent installer.
- Double-click the Phoenix installer.
- Click Next.
- 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:
Step 2: (Optional) Configure Web proxy on Windows
Phoenix agent communicates with Phoenix Cloud through the internet to perform authentication, activation, and registration. If your server falls under a network configuration that uses a Web proxy, it is possible that Phoenix agent fails to communicate with Phoenix Cloud because of your network settings. Perform the following steps to configure the Phoenix agent so that it can communicate with Phoenix Cloud through the Web proxy in your network infrastructure.
Before you begin, ensure that Phoenix agent is installed and running before you start proxy settings.
Configure Web proxy
- Open the command line interface window.
- In the command line interface, change the directory with which the CLI opens to the directory where Phoenix agent is installed.
By default, Phoenix agent is installed on: C:\Program Files\Druva\Phoenix Agent.
For example, to change directory in CLI, you run: cd “C:\Program Files\Druva\Phoenix Agent”
- On command prompt, run the following command:
PhoenixControl.exe set_proxy_details -t proxy_type -i proxy_IP:port -u proxy_user -p proxy_password
Druva supports the following proxy types:
Valid IP of the proxy server.
Respective proxy port number.
Valid proxy user name.
Valid proxy password.
- Web proxy is installed successfully.
Note: Druva only supports basic authentication with Web proxy.
- The Threat Management Gateway (TMG) drops IDLE connections after defined timeout duration, due to which agent does an aggressive retry with server.
Note: In TMG application, it is recommended to set connection timeout value to 5 minutes.
- The configuration file path for Phoenix Client and Cache Server are as follows:
For windows agent: C:\ProgramData\Phoenix\Phoenix.cfg
- 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: Generate the activation token
- Log on to the Phoenix Management Console,
- On the menu bar, click All Organizations, and select the organization in which you want to add your MS-SQL server.
- On the menu bar, click Protect > Windows/Linux Servers and click Register New Server.
- When you click Register New Server, the Register Server wizard opens. The Register Server wizard contains three sections: Install Druva Phoenix Agent, Generate Activation Token, and Server Activation.
- The Install Druva Phoenix Agent section lets you download the agent executable that you run on your server to install the agent.
- click Next. The Generate Activation Token section lets you specify a token description, the number of servers you want to register, and set a validity of the token. By default, can use a token to register 25 servers within 7 days.
- The Server Activation section displays the activation token required to activate the agent. Copy the activation token, and click Finish.
Note: Phoenix lists the activation token under Manage > Activation Tokens.
Step 4: Activate the agent
After you install Phoenix agent on a Windows server, you must activate that Phoenix agent using the activation token that Phoenix generated at the time of registering servers. The token functions as a unique identifier and performs a one-time authentication of Phoenix agents.
After authentication, Phoenix agents establish a persistent connection with Phoenix Cloud.
Note: We recommend that you use a single token to activate servers that share something in common. For example, you might want to use a token to activate all servers that are geographically co-located.
- Copy the activation token that Phoenix generated.
- Double-click the Phoenix agent shortcut. The Druva Phoenix window is displayed:
- Enter the following details:
Enter Activation Token
Enter the activation token generated while registering server.
A unique server name.
Note: The server name should not contain any special characters.
Note: If you are activating the Phoenix agent for Phoenix Cloud, do not select the GovCloud check box.
- Click Activate.
Note: Set the client to standard time zone.
- For the client version below 4.0, if you set the client to a local time zone, you will get an "Internal Error".
- For the client version 4.0 and above, if you set the client to a local time zone, you will get the following error.
If you choose to mass deploy Phoenix agents using third-party tools, you can use the command-line method to activate the Phoenix agent. By default, the agent PhoenixControl.exe is located at the C:\Program Files\Druva\Phoenix Agent location. To activate the client, you can run PhoenixControl.exe from any location.
From the command prompt, run the following command:
- For Phoenix Cloud:
PhoenixControl.exe activate <token> --ServerName <ServerName>
where <token> represents the activation token that Phoenix generated at the time of registering the server.
- For GovCloud:
PhoenixControl.exe activate govcloud <token> --ServerName <ServerName>
Note: 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 upgrade Phoenix agents to their latest available version. For more information, see Agent upgrades.
On the Phoenix Management Console, the activated server is registered under the organization you selected in step 1. To see the instances or the availability group available for the server, log on to Phoenix Management Console, select the organization, and click Protect > MS-SQL Servers > Instances/AGs tab.
After your SQL server is registered, you can configure it for backup.