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

Following sections provide the software requirements for Phoenix to back up data residing on servers.

Operating systems for file and folder backup

The certified and supported platforms on which Phoenix can backup and restore files and folders are listed in the following sections.

Certified platforms

Operating system File system Editions

Windows

(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) 

Windows

(Standard edition)

New Technology File System (NTFS)

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

Linux

 

  • 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)

Ubuntu

 

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

Linux

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

Druva provides vendor-agnostic support for NAS devices. The supported protocol for SMB and NAS shares is as mentioned below. Phoenix can perform backup and restore provided your configuration adheres to the following  NAS proxy mappings.

NAS share type Backup and restore with NAS proxy on Windows Backup and restore with NAS proxy on Linux
SMB Yes No
NFS No Yes
Mixed No No

Since you install the NAS proxy on a Windows or Linux server, the server must comply with the following requirements.

Certified platforms

Druva certifies backup and restore through NAS Proxy installed on the following platforms.

Operating system Edition Support considerations

Windows

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

Phoenix supports backup and restore from all SMB share versions supported on the respective Windows Server version.

Linux

  • CentOS 6.3,  6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1 and 7.2 (x86-64)
  • Ubuntu Server 14.04, 16.04 (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)

Phoenix supports backup and restore from all NFS share versions supported on the respective Linux Server version and variants.

Supported platform

Druva supports backup and restore through NAS Proxy installed on the following platforms.

Operating system Edition Support considerations

Linux

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

Phoenix supports backup and restore from all NFS share versions supported on the respective Linux Server version.

Ports and communication protocols for Phoenix

Phoenix communicates with your NAS shares to back up and restore the data. This occurs through ports and protocols that are secure for communication and transition of data. Phoenix uses Transport Layer Security (TLS) protocol to establish a connection and initiate communication between Phoenix components and your NAS device.

The following diagram depicts the ports and communication protocols that Phoenix uses for secure connection and communication during the backup and restore operations. 

PortsAndCommunicationProtocols.png

Support matrix for Hyper-V

Druva categorizes its platform support levels as follows:

  • Certified Platforms: Druva certifies these environments and performs regular verification to ensure the functionalities work as expected.
  • Supported Platforms: The Druva QA team does not test a supported platform with every cloud release. However, the functionality should work as expected. Druva will provide support for such platforms. Druva may not address issues that require time and resources beyond commercial viability.

Certified platforms

Windows Server (64-bit)

(Standard and Enterprise editions)

Microsoft Windows Server 2016
Microsoft Windows Server 2012 R2 
Microsoft Windows Server 2012
Microsoft Windows Server 2008 R2

Supported platforms

Windows Server (64-bit)

(Standard and Enterprise editions)

Microsoft Windows Server 2008
Note: 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. 

Hardware requirements for Phoenix agent on Windows

See, Hardware requirements.

Partition type and file systems for file-level restore (FLR) 

Windows:

  • Primary

  • Extended

  • Basic disk (Partition type: MBR/GPT)

  • Dynamic disk (Partition type: MBR. (simple/spanned volume)

Note: Dynamic Disk with GPT partition type is not supported.

Linux:

LVM (Simple/Spanned/Mirror/Stripped)

File-systems:

  • NTFS

  • FAT

  • FAT32

  • Ext2/3/4

  • XFS

System requirements for FLR proxy 

Before you deploy and activate the FLR proxy, ensure that following system requirements on the Hyper-V host are met for the proxy:

  • Memory: 2 GB
  • vCPUs: 2

This is a recommended  configuration for two restore jobs. If you want to run multiple restore jobs, increase the memory and number of vCPUs. 

SQL server editions  

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.

Certified platforms

Druva certifies the following editions:

  • Windows Server (64-bit) Standard and Windows Server (64-bit) Enterprise edition operating systems
  • SQL Server Enterprise edition

Windows Server (64-bit)

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

For more information on hardware requirements for Phoenix agent, see Hardware requirements

Supported platforms

Druva supports SQL Server Standard editions of the versions listed above. 

For more information, see System requirements.

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.5
  • 6.0
  • 5.5

Standard

6.0

  • 6.0
  • 5.5
  • 5.1

Standard

 

 

5.5

  • 5.5
  • 5.1

Standard

Supported Platform

Following table lists the Supported versions for vCenter.

Supported versions License Type
5.1 Standard

Hardware requirements

Prerequisites for Phoenix agent

This section contains the prerequisites for the Phoenix agent. Applies to: 

  • Hyper-V
  • Files on a server
  • NAS Shares
  • MS-SQL servers

Hardware prerequisites for installing Phoenix agent

Hardware Minimum Requirement

CPU

2 GHz dual-core (Intel Core series)

2.4 GHz (AMD) or equivalent

RAM 4 GB

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
      C:\ProgramData\Phoenix
    • Windows 2008 Server
      C:\ProgramData\Phoenix
    • Linux
      • /var/log/Phoenix
      • /var/Phoenix 
  • On Windows servers, minimum 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 http://downloads.druva.com/phoenix/.

You can also download the installer at the time of registering servers. 

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)
RAM 6 GB
Virtual disks 4 virtual disks (40 GB, 30 GB and 2 disks with 1 MB 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 http://downloads.druva.com/phoenix/.

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 "*.druva.com". 
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 

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.

Conclusion 

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.