Skip to main content


Druva Documentation

Support matrix

Before you set up Phoenix, you must ensure that the virtual machines or the servers that you plan to use, meet the system requirements.

This article gives you information about:

Support levels 

Druva categorizes its platform support levels as follows:

  • Certified platforms: A certified platform is fully tested by Quality Assurance (QA) team. Druva certifies these environments and performs regular testing with every cloud release to ensure the functionality works as expected.
  • Supported platforms: A supported platform is not tested by the Druva QA team with every cloud release, however, the functionality should work as expected. Druva will provide support for such platforms. Issues that require time and resources beyond commercial viability may not be addressed.

Browser support 

The following table lists the supported browsers for accessing the Phoenix Management Console.

Browser Minimum requirement

Web browser

  • Internet Explorer (IE) 11 and Edge
  • Mozilla Firefox (Firefox) 33
  • Google Chrome (Chrome) 35

Note: Druva recommends that you use Firefox or Chrome for accessing the Phoenix Management Console. If you use Internet Explorer, some UI elements might not appear as expected. 

Software requirements

File server operating systems

Certified platforms

Operating system File system Editions


(Standard and Enterprise editions)


New Technology File System (NTFS)


  • Windows Server 2016 (x86-64) 
  • Windows Server 2012 R2 (x86-64) 
  • Windows Server 2012 (x86-64)
  • Windows Server 2008 R2 (x86-64) 
  • Windows Server 2008 (x86-64) 


(Standard edition)

New Technology File System (NTFS)

Windows Small Business Server ( SBS) 2011 (x86-64)



  • Extended file system (EXT) version 3 and 4
  • XFS
  • CentOS 6.3,  6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1 and 7.2 (x86-64)
  • Red Hat Enterprise Linux (RHEL) 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1 and 7.2 (x86-64)



Extended file system (EXT) version 3 and 4


  • Ubuntu 14.04 (x86-64)
  • Ubuntu 16.04 (x86-64)

Supported platforms

Operating system File system Editions



Extended file system (EXT) version 3 and 4


  • Oracle Linux 6.8 (x86-64)
  • SUSE Linux Enterprise Server (SLES) 11.4 and 12.2 (x86-64)

Support matrix for NAS devices

Support Matrix for NAS proxy

SQL server editions  

Windows Server (64-bit)

(Standard and Enterprise editions)

SQL server editions

Windows Server 2016 (x86-64)

  • SQL Server 2016 SP1 
  • SQL Server 2014

Microsoft Windows Server 2012 R2

  • SQL Server 2016 SP1
  • SQL Server 2014
  • SQL Server 2012 Service Pack (SP) 2
  • SQL Server 2008 Service Pack (SP) 4
  • SQL Server 2008 R2 SP 3

Microsoft Windows Server 2012 

  • SQL Server 2016 SP1
  • SQL Server 2012 SP 2
  • SQL Server 2008 R2 SP 3
  • SQL Server 2008 RTM

Microsoft Windows Server 2008 R2 SP 1

  • SQL Server 2012 SP 2
  • SQL Server 2008 RTM

Microsoft Windows Server 2008 R2

  • SQL Server 2008 R2 SP 3
  • SQL Server 2008 RTM

Microsoft Windows Server 2008 SP 2

  • SQL Server 2012 SP 2
  • SQL Server 2008 R2 SP 3
  • SQL Server 2008 RTM

Microsoft Windows Server 2008

  • SQL Server 2008 SP 4
  • SQL Server 2008 RTM

VMware infrastructure

This section lists the Certified and Supported versions for VMware vCenter Server and ESXi Hosts.

Certified Platform

vCenter Server ESXi Host License


  • 6.5
  • 6.0
  • 5.5



  • 6.0
  • 5.5
  • 5.1





  • 5.5
  • 5.1



Supported Platform

Following table lists the Supported versions for vCenter.

Supported versions License Type
5.1 Standard

Hardware requirements

Prerequisites for File servers and SQL servers 

This section contains the prerequisites that are common for File servers and SQL servers.

Hardware prerequisites for installing Phoenix agent

Hardware Minimum Requirement


2 GHz dual-core (Intel Core series)

2.4 GHz (AMD) or equivalents


Free space

  • On Windows and Linux servers, 2% of the total source data is utilized for Phoenix application data. This application data is stored in the following locations:
    • Windows 2012 Server
    • Windows 2008 Server
    • Linux
      • /var/log/Phoenix
      • /var/Phoenix 
  • On Windows servers, 10% of each volume size that you want to backup for Volume Shadow Copy Service (VSS) snapshots.

Phoenix agent installer 

The Phoenix agent installer is available at

You can also download the installer at the time of registering servers. For more information, see Register a server.

Disks, partitions and, files for File Level Restore (FLR)

Item Certified

Disk Types

  • Thin
  • Thick

Partition Tables

  • MBR
  • GPT (Linux)

Partition Types

  • Primary
  • Extended
  • LDM (Only Simple and Spanned Volumes with MBR)
  • LVM (Simple/Spanned/Mirror/Striped)

File Systems

  • NTFS
  •  FAT
  •  FAT32 
  •  Ext2/3/4 
  • XFS

File Type

  • Regular Files
  • Sparse Files
  • Hidden Files

Prerequisites for VMware 

This table lists the minimum requirements for deploying backup proxy that is available as a virtual appliance. 

Backup proxy requirements 

Backup proxy is available as a virtual appliance. Deploying backup proxy creates a virtual machine with the configuration that is listed in this table. Ensure that your VMware setup can assign resources to support this requirement. 

Parameter Default configuration
vCPU 8 vCPU (2 virtual sockets with 4 cores per socket)
Virtual disks 4 virtual disks (40GB, 30GB and 2 disks with 1MB each).

With the above default configuration, you can backup up to three virtual machines in parallel. For more information, see Sizing for backup proxy.

Backup proxy virtual appliance 

Backup proxy is available as an OVF virtual appliance at

You can also download the installer at the time of registering backup proxy.

Network requirements 

Field Requirement

Network Traffic rules

Phoenix agent:

Outgoing network traffic: Phoenix agents connect to Phoenix cloud using port 443.

Phoenix CloudCache:  

Outgoing network traffic: Phoenix CloudCache connects to Phoenix cloud using port 443.

Incoming traffic: Phoenix agents connect to Phoenix CloudCache using port 443. 

Firewall  For all the agents and CloudCache: If the firewall is enabled, allow all outgoing TCP/IP traffic to port 443 for "*". 
Web proxy Druva supports the following proxy types:
  • http
  • socks4
  • socks5

For more information see:

Security considerations 

One thing that is often overlooked when deploying a data protection solution is security. While Druva automatically handles the security of information in transit and at rest, there are other security mechanisms that organizations should consider for implementing beyond encryption when it comes to data protection. The following sections discuss the security considerations that organizations should take into account as they implement Phoenix for their data protection solution.

Roles and responsibilities 

In order to prevent privileged users from making unauthorized changes to resources within their organization, Phoenix supports the Role Based Access Control (RBAC) for separation of duties. This capability allows organizations to limit privileged user access to a predefined set of roles and data assets. This RBAC capability makes it possible to create ethical walls to enforce privacy, as well as implement a delegated administration structure to meet customers’ organizational, compliance, or security requirements. To add RBAC in your Phoenix deployment, see Manage administrators.

Global regulatory compliance 

As part of your data protection strategy, organizations need to take into account where they operate and what requirements they have on security and availability of the data.  With Druva Phoenix, organizations can store data in any of twelve global regions depending on their security, compliance, data access, and availability requirements. While not only a compliance requirement, proximity to data can also help shrink the time it takes to recover in the event of a disaster.

Single sign-on 

Phoenix supports SAML which allows organizations to centralized authentication for the administration of their Phoenix environment. This allows Phoenix administrators to leverage existing centralized authentication mechanisms like Okta, Ping Identity, or Active Directory which are already being used today.  The use of Single sign-on (SSO) helps to guarantee the availability of access to Phoenix and eliminates local authentication stores which cause audit and compliance headaches as well as create a security risk. To integrate Phoenix with your SSO authentication mechanism, see Configure single sign-on for Phoenix.

Testing your recovery 

As part of your data protection strategy, it is important to see if what you are backing up is actually getting backed up, whether part of a normal business continuity and disaster recovery process.


While protecting data in flight and at rest are important security capabilities of any enterprise-level data protection solution, there are definitely more issues to take into account, and more capabilities to take advantage of when it comes to protecting the overall data attack surface. For identifying and implementing more such security considerations for Phoenix, contact Druva Support.