Skip to main content
Druva Documentation

Install the Phoenix agent on a SQL Failover Cluster Instance (FCI)

This article contains the instructions on installing and configuring Phoenix on a SQL failover cluster environment which has multiple nodes.


A shared storage that is configured and accessible to the cluster and all nodes.


On a high level, there are five steps to configure Phoenix for the backup of a SQL failover cluster. As an example for this article, there are three nodes in the cluster, NODE01, NODE02, and NODE03.

  1. Add the shared disk to all the cluster nodes
  2. Configure clustered shared volume to install Phoenix
  3. Install Phoenix agent on the shared drive
  4. Add Phoenix client service as SQL Failover Cluster Instance Resource
  5. Ensure that Phoenix service is active only on the node where FCI is running

The following flow diagram summarizes the procedure for configuring Phoenix for the backup of a node-based SQL failover cluster:


1. Add the shared disk to all the cluster nodes

  1. Log on to the NODE01 machine.
  2. Launch the Disk Management console.
  3. Right-click on the shared disk and select Online to bring it online.
  4. Right-click again on the disk and start the New Simple Volume Wizard.
  5. On the first dialog, click Next.
  6. Specify the Simple Volume Size in MB. Click Next.
  7. For easier access, assign a drive letter to the disk; for example, P and click Next.
  8. Enter a volume label in the Volume Label text box; for example, Phoenix and click Next
  9. Click Finish and wait for a few seconds for the format operation to complete. Your disk is formatted with the NTFS file system.

2. Configure clustered shared volume to install Phoenix

  1. Launch the Failover Cluster Manager console.
  2. On the left pane, expand Storage and select Disks.Failover_cluster_manager.png
  3. Click Add Disk in the Actions pane on the right-hand side. You can see your newly added shared disk in the pop-up window. Select the disk and click OK. Add_disk_to_a_cluster.png
  4. In the Disks section, right-click on the disk and select Properties. Rename the disk as PhoenixDisk (or any name that you may prefer). Click Apply and OK. PhoenixDisk.png
  5. Right-click on the disk and select Add to Cluster Shared Volumes. The drive is added to your node. Now, the drive is added as a CSVFS disk. Assign a letter to this disk.
  6. Before you can assign a letter to the disk, the Owner Node of the disk must be the same as the node you have logged on to (in this case NODE01). To ensure that NODE01 is the Owner Node:
    1. Select the CSVFS disk (in this example, the disk with PhoenixDisk as its name).
    2. After you select the disk, click Move Available Storage > Select Node.
    3. On the Move Cluster Shared Volume dialog box that appears, select the node you are logged on to (NODE01 in this example).  
  7. To assign a letter to this disk, launch the Disk Management console.
  8. On the Disk Management console, right-click on the shared disk and launch the New Simple Volume Wizard. Follow the steps in the wizard and assign a letter to the disk (for example, P).

3. Install Phoenix agent on the shared drive

  1. Download the Installer for Windows 64-bit Phoenix Cloud agent on all nodes in the cluster.
  2. Log on to NODE01. For the sake of simplicity, assume that drive P: is the shared drive that you have created as clustered shared volume across all nodes on which you want to install Phoenix.
  3. Start the installation for Phoenix using the downloaded Installer.
  4. Accept the license and click Next
  5. If you want to use a domain account, disable the Use Local System Account option and provide the domain account credentials. Provide the domain account username in the format: domain\username
  6. In the Install Location box, enter the directory of the shared storage; for example, if P: drive is your shared directory, replace C with P and click Install. The Installer copies all the necessary files on the given shared directory P:.
  7. Click Finish after installation is complete. Phoenix is now installed on the P: drive.
    If you use the domain user account at the time of installing the agent, ensure that you manually upgrade the agent when an upgrade is available. The Phoenix agent loses the domain account credentials if the agent is upgraded automatically and the log backups fail with the SQL7 error. To manually upgrade the agent, download and install the latest agent on the server and provide the domain user account credentials at the time of installing it.
  8. Stop the Phoenix service.
  9. Go to the C:\ProgramData directory. Move the Phoenix folder to the shared directory P:; for example, move it to P:\SharedProgramData\.  

    Note: This step of moving the “Phoenix” Folder is required only at the first login on the first node. For the next nodes, you can delete the Phoenix Folder from C:\ProgramData directory after stopping Phoenix service as you have moved the Phoenix folder to the shared location P:\SharedProgramData which is to be made accessible to all nodes.

  1. To make Phoenix access its local data and configuration files, create a junction point that points to the newly created Phoenix folder location on the shared drive P\SharedProgramData\Phoenix. This step must be performed on all nodes. Open Command Prompt and create a junction point using the following command:

    Mklink /j C:\ProgramData\Phoenix P:\SharedProgramData\Phoenix
  2. Log on to the next node, NODE02, and follow the steps from 2 through 9 to install Phoenix.

    • If you have a configuration with more than two nodes, you must install Phoenix on all the nodes by following the steps through 2 to 9. You must maintain the same folder structure on all nodes for installing Phoenix.
    • After the installation is complete, stop the Phoenix service on all the nodes except the active node that you are going to register and configure with Phoenix. For example, if you are planning to register your SQL failover cluster client using NODE01, which is the active node, Phoenix Service must be stopped on all the other passive nodes. Phoenix service should be started on active node NODE01.
  3. Register NODE01 and configure it for backup. To know the procedure for registering a server, refer to Register a Server.

4. Add Phoenix Client service as a SQL Failover Cluster Instance Resource

  1. Open Failover Cluster Manager and select Roles in the left pane.
  2.  Right-click on the SQL Server role and click Add Resource > Generic Service. The New Resource Wizard pop-up window appears.
  3. Select  Druva Phoenix Agent Client Service from the list of services displayed and click Next.
  4. The Confirmation section on the pop-up window appears. Verify the details and click Next to continue.
  5. The Configure Generic Service section on the pop-up window appears. Verify the details and click Next to continue.
  6. In the Summary section, to view the report created by the wizard, click View Report. Click Finish

5. Ensure that Phoenix service is active only on the node where the FCI cluster is running

Ensure that the Phoenix service is active only on the node where the FCI cluster is running. Stop the Phoenix service on the rest of the nodes in the cluster. This is required for Phoenix service failover.

To configure the Phoenix agent to use the Microsoft CSV Shadow Copy Provider, see How do I make the Phoenix agent use the Microsoft CSV Shadow Copy Provider?

You are now ready to back up your SQL failover cluster. Follow the steps described in Configure registered servers for backup for creating a SQL backup set.