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:

Browser support

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

Browser Minimum requirements

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

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

Software requirements for files and folders

Phoenix supports the File servers running with Windows and Linux operating systems as well as the network shares. The following table lists the supported platforms that Phoenix can backup and restore files and folders on.

Operating System

File System

Editions

Windows

(Standard and Enterprise editions)

 

New Technology File System (NTFS)

 

  • Windows Server 2019 (64-bit)
  • Windows Server 2016 (64-bit) 
  • Windows Server 2012 R2 (64-bit) 
  • Windows Server 2012 (64-bit)
  • Windows Server 2008 R2 (64-bit) 
  • Windows Server 2008 (64-bit ) 

Windows

(Standard and Enterprise editions)

 

Resilient File System (ReFS) 1.1, 1.2, 2.0, 3.0, 3.1

 

  • Windows Server 2019 (64-bit)
  • Windows Server 2016 (64-bit) 
  • Windows Server 2012 R2 (64-bit) 
  • Windows Server 2012 (64-bit)

Windows

(Standard edition)

New Technology File System (NTFS)

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

Linux

 

  • Extended file system (EXT) version 3 and 4
  • XFS
  • CentOS 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, and 7.6 (64-bit)
  • Red Hat Enterprise Linux (RHEL) 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, and 7.4, 7.5, and 7.6 (64-bit)
  • Oracle Linux 6.8, 6.9, 6.10, 7.5, and 7.6 (64-bit)
  • SUSE Linux Enterprise Server (SLES) 11.4, 12.2, and 12.4 LTS (64-bit)

Ubuntu

 

Extended file system (EXT) version 3 and 4

 

  • Ubuntu 14.04 (64-bit)
  • Ubuntu 16.04 (64-bit)
  • Ubuntu 18.04 LTS (64-bit)

Ports and communication protocols for Phoenix 

Phoenix communicates with your File servers to backup and restores the data from your File servers. This communication happens through ports and protocols that are secure for communication and transition of data.

Phoenix uses Transport Layer Security (TLS) protocol for establishing a connection and initiating communication between Phoenix components and your File servers.

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

port_and_protocol_for_file_server_setup1.png

Software requirements for Hyper-V

This section contains information about the Windows server that Phoenix supports.

Operating System

Editions

Windows

  • Windows Server 2016 (Standard and Datacenter editions)
  • Windows Server 2012 R2  (Standard and Datacenter editions)
  • Windows Server 2012  (Standard and Datacenter editions)
  • Windows Server 2008 R2  (Standard and Enterprise editions)
  • Windows Server 2008 (Standard and Enterprise editions)
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. 

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

Software 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. 

Ports and communication protocols for Phoenix 

Phoenix communicates with your hosts to backup and restore data on your hosts. Phoenix talks to your Hyper-V host through ports and protocols that are secure for communication and transition of data.

Phoenix uses Transport Layer Security (TLS) protocol for establishing the connection and initiating communication between Phoenix components and your Hyper-V hosts.

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

port_and_protocol_for_hyperV.png

Software requirements for MS SQL servers

Druva supports the following editions:

  • Windows Server (64-bit) Standard and Windows Server (64-bit) Enterprise edition operating systems
  • SQL Server Enterprise edition
  • SQL Server Standard editions of the versions listed below running on certified Windows Servers. 
  • Backup and restore of databases encrypted with Transparent Data Encryption (TDE).

Windows Server (64-bit)

SQL Server Editions

Windows Server 2016 SQL Server 2017

Windows Server 2016
 

  • 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

Microsoft Windows Server 2008 R2 SP 1

  • SQL Server 2012 SP 2
  • SQL Server 2008

Microsoft Windows Server 2008 R2

  • SQL Server 2008 R2 SP 3
  • SQL Server 2008

Microsoft Windows Server 2008 SP 2

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

Microsoft Windows Server 2008

  • SQL Server 2008 SP 4
  • SQL Server 2008

Software requirements 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/CIFS Yes No
NFS No Yes
Mixed No No

Software requirements for NAS proxy 

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

Operating System

Edition

Support Considerations

Windows

  • Windows Server 2019 (64-bit)
  • Windows Server 2016 R2 (64-bit) 
  • Windows Server 2012 R2 (64-bit) 
  • Windows Server 2008 R2 (64-bit) 

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, 6.9, 6.10 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, and 7.6 (64-bit)
  • Ubuntu 14.04, 16.04 , 18.04 LTS (64-bit)
  • Red Hat Enterprise Linux (RHEL) 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.4 , 7.5, and 7.6  (64-bit)
  • Oracle Linux 6.8, 6.9, 6.10, 7.5, and 7.6 (64-bit)
  • SUSE Linux Enterprise Server (SLES) 11.4 and 12.2 (64-bit)

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

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

Software requirements for Oracle 

Phoenix supports the following Oracle instances:

Standalone instance

Oracle Database Versions

Host Operating Systems (64-bit)

Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64-bit Production

CentOS 7.3

Red Hat Enterprise Linux Server 7.1

Oracle Linux Server 7.0

Windows Server 2016

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64-bit Production

Red Hat Enterprise Linux Server 7.2

Oracle Linux Server 6.10

Windows Server 2012 R2 Standard Edition

Windows Server 2008

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64-bit Production

Red Hat Enterprise Linux Server 6.7

Real Application Cluster

Oracle Database Versions

Host Operating Systems (64-bit)

Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64-bit Production

Oracle Linux Server 7.3 (Maipo)

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64-bit Production

CentOS 6.4

System requirements for the Phoenix Backup Store 

Ports and communication protocols for Phoenix

The Phoenix Backup Store takes incoming requests on port 9090. Since the RMAN communicates with the Phoenix Backup Store API to check the status, ensure that the port 9090 on the Phoenix Backup Store can take incoming requests over http.

In addition, ensure that the firewall allows RMAN to write to the backup mount on the Phoenix Backup Store. To check which ports you need to open on the RMAN host, run:


rpcinfo -p | grep nfs

Phoenix Cloud communicates with the Phoenix Backup Store to backup and restore data on it. To backup and restore data, the Phoenix Cloud communicates to the Phoenix Backup Store through ports and protocols that are secure for communication and transition of data.

Phoenix uses Transport Layer Security (TLS) protocol for establishing the connection and initiating communication between Phoenix components.

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

network_protocols.png

Note: If a firewall is set up, allow outbound TCP/IP traffic to *.druva.com through port 443. 

Software requirements for VMware     

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

VMware vCenter server and ESXi host versions

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

vCenter Server

ESXi Host

License

6.7

  • 6.7
  • 6.5
  • 6.0

Standard

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

5.1

  • 5.1

Standard

Standalone ESXi Host

This section lists the supported versions for Standalone ESXi Host.

Standalone ESXi Host

License Type

6.7

Standard

6.5

Standard

6.0

Standard

5.5

Standard

5.1

Standard

Note: To backup virtual machines hosted on vCenter and ESXi versions 6.5, use backup proxy version 4.6.9-27415 or later.

Backup proxy compatibility

The following table describes the virtual machines backup support corresponding to backup proxy deployed on specific vCenter and ESXi versions:

Backup Proxy Version

Backup Proxy Compatibility

4.7.2-42700 or later

vCenter or ESXi versions:

  • 6.7
  • 6.5
  • 6.0
  • 5.5
  • 5.1

4.6.9-27415 to 4.7.2-42106

vCenter or ESXi versions:

  • 6.5
  • 6.0
  • 5.5
  • 5.1

Versions older than 4.6.8-20739

vCenter or ESXi versions:

  • 6.0
  • 5.5
  • 5.1

If a backup proxy is deployed on an incompatible vCenter or ESXi version, virtual machine backup jobs will fail. 

Guest operating systems

Phoenix supports the following operating systems.

Operating System

Editions

Windows

  • Windows Server 2012 R2 (64-bit) 
  • Windows Server 2012 (64-bit)
  • Windows Server 2008 R2 (64-bit) 
  • Windows Server 2008 (64-bit) 

Linux

  • CentOS 6.3 - 6.4, 7.0 - 7.2 (64-bit)
  • Red Hat Enterprise Linux (RHEL)6.3 - 6.4, 7.0 - 7.2  (64-bit)

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

Item

Supported

Partition Types

  • Primary
  • Extended
  • Logical Disk Manager (LDM): 
    • Windows
      • Basic disk (Partition type: MBR/GPT) 
      • Dynamic disk (Partition type: MBR. Partition can have simple or spanned volume.)
        Note: Dynamic Disk with GPT partition type is not supported.
    • Linux
      • MBR  (Simple/Spanned/Mirror/Striped) 
      • GPT (Simple/Spanned/Mirror/Striped)

File Systems

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

File Type

  • Regular Files
  • Sparse Files
  • Hidden Files

vSAN versions

Phoenix backup proxy supports backup and restore of virtual machines on the following vSAN versions:

  • 6.6
  • 6.5

Ports and communication protocols for Phoenix 

Phoenix communicates with your virtual infrastructure to backup and restore virtual machine data. This communication happens via ports and communication protocols that are secure for communication and transition of data.

Phoenix uses a combination of Transport Layer Security (TLS) and Secure Socket Layer (SSL) protocols for establishing a connection and initiating communication between Phoenix components and your virtual infrastructure components such as vCenter Server, ESXi hosts, and virtual machines.

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

The following table describes the port and communication protocols used for communication between Phoenix and various VMware components.

Port/Communication Protocol

Description

443

Phoenix uses Port 443 to establish a secure connection and communication between the following:

  • Backup Proxy to Phoenix Cloud
  • Backup Proxy to Phoenix CloudCache
  • Backup Proxy to vCenter Server
  • Backup Proxy to ESXi host
    Note: Backup proxy establishes connection with ESXi host over Port 443 only if it registered with Phoenix as Standalone ESXi. If the ESXi host is registered with Phoenix through vCenter Server, backup proxy communicates with the ESXi host over Port 902.

902

Phoenix uses Port 902 to establish a connection between the backup proxy and ESXi host registered with Phoenix through vCenter Server.

3389/22

 

During the backup cycle, the backup proxy sends network packets to Windows virtual machines (where VMware tools are installed) on port 3389 to identify if the RDP port is open or not. For Linux virtual machines, the port is 22, which is used for SSH.

This is used for Phoenix DRaaS or DR restores.

123 (UDP) Backup proxy accesses NTP server on Port 123 (UDP) for time synchronization.

TLS

Phoenix uses TLS for a secure connection that happens between the following:

  • Backup proxy and Phoenix Cloud
  • Backup proxy and Phoenix CloudCache
  • Phoenix CloudCache and Phoenix Cloud

SSL

Phoenix uses SSL for a secure connection that happens between the following:

  • Backup proxy and vCenter Server
  • Backup proxy and ESXi hosts

Software requirements for Phoenix CloudCache

The following table lists the system requirements for deploying Phoenix CloudCache.

Operating system

Editions

Windows

  • Windows Server 2012 R2 Standard Edition (64-bit)
  • Windows Server 2016 (64-bit)

Ports and communication protocols for Phoenix 

Phoenix CloudCache communicates with your servers and Phoenix Cloud to back up and restore the data. This communication happens through ports and protocols that are secure for communication and transition of data.

Phoenix CloudCache uses Transport Layer Security (TLS) protocol to establish a connection and initiate communication with Phoenix components.

The following diagram depicts the ports and communication protocols that are used by Phoenix CloudCache for secure connection and communication during the backup and restore operations.

Hardware requirements

The Phoenix agent installer, VMware backup proxy appliance, Hyper-V FLR proxy appliance, Phoenix Backup Store package, and the CloudCache installer are available at http://downloads.druva.com/phoenix/.

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

Prerequisites for Phoenix agent 

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

  • Hyper-V virtual machines
  • Files on a server
  • NAS Shares
  • MS-SQL servers
Hardware requirements for installing Phoenix agent 
Hardware Minimum requirements

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, a minimum 10% of each volume size that you want to backup for Volume Shadow Copy Service (VSS) snapshots.

Hardware requirements for Hyper-V 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. 

Disks, partitions, and files supported for File Level Restore (FLR) on Hyper-V hosts
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

Hardware requirements  for NAS shares

The following table describes the hardware specifications that the Phoenix agent requires to back up one backup set:

Hardware

Minimum Requirement

CPU

  • Three Cores or,
  • Three vCPUs if the agent is installed on a virtual machine

RAM

3 GB

Free space

  • On Windows and Linux servers, 2% of the total source data is utilized for the 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 

 By default, the Phoenix agent is configured to run six backup sets in parallel.

Hardware requirements for VMware  

This table lists the minimum requirements for deploying a 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.

Hardware requirements for the Phoenix Backup Store 

You can set up a Phoenix Backup Store on:

  • An Ubuntu server: Deploy the Debian package that Druva provides on an Ubuntu server and use the Ubuntu server as a Phoenix Backup Store.
  • A VMware setup: Deploy the Open Virtual Appliance (OVA) package that Druva provides on a supported VMware/ESXi host and start the virtual machine. Use this virtual machine as a Phoenix Backup Store.
  • Amazon Web Services (AWS): Deploy the Debian package that Druva provides on an EC2 instance with Ubuntu operating system to use the EC2 instance as a Phoenix Backup Store. 

The following sections provide a recommended configuration of a system that you can use as a Phoenix Backup Store.

Ubuntu server as a Phoenix Backup Store

This table provides a recommended configuration of the Ubuntu server on which you deploy the Debian package to use the server as a Phoenix Backup Store.

Hardware/Software

Specification

Operating system Ubuntu 18.04 (64-bit)
CPU 8 Cores
RAM 6 GB
Hard disks At-least 300 GB. 
ZFS pool configuration RAIDZ (Requires at-least three disks)
You can create a ZFS pool with less than three disks using RAID0 configuration.
ZFS compression LZ4
ZFS deduplication Off
ZFS record size 128 KB

A virtual machine on a VMware vCenter/ESXi as a Phoenix Backup Store

The following table describes the recommended configuration of the virtual machine that you create using the OVA package that Druva provides, and use it as a Phoenix Backup Store. 

Hardware/Software

Specification

vCenter/ESXi versions 6.7/6.5/6.0
vCPU 8 Cores
RAM 8 GB
Virtual disk The OVA contains 3 virtual disks. Two disks of 100 GB capacity each to create the ZFS pool for backup and the third disk (sdd) of 200 GB capacity for restore. 
ZFS pool configuration RAIDZ (Requires at-least three virtual disks)
You can create a ZFS pool with the two attached disks using RAID0 configuration.
ZFS compression LZ4
ZFS deduplication Off
ZFS record size 128 KB

An AWS EC2 instance as a Phoenix Backup Store

The following table describes the recommended configuration of the AWS EC2 instance on which you can deploy the Debian package and use it as a Phoenix Backup Store. 

Hardware/Software

Specification

Instance type c5.4xlarge
Operating system Ubuntu 18.04 (64-bit)
CPU 16 Cores
RAM 16 GB
EBS Volume At-least 500 GB on a ThroughPut optimized HDD (ST1). 
 
ZFS pool configuration RAIDZ (Requires at-least three volumes)
You can create a ZFS pool with less than three volumes using RAID0 configuration.
ZFS compression LZ4
ZFS deduplication Off
ZFS record size 128 KB


Hardware requirements for Phoenix CloudCache

Prerequisite

Minimum Requirement

CPU

64-bit, quad-core processor

RAM

8 GB or greater

Network Traffic rules

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

Firewall

If a 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:

 Note:  Phoenix does not support 4K native drives in the CloudCache environment. We recommend you to use 512 native drives for backup.    

To use Phoenix CloudCache 3.3-7649 or later, install the following agents on the servers that you want to protect:

  • Linux RPM version 4.6.1-7433 or later.
  • Windows 64/32 bit agent version 4.6.1-7430 or later.

  If you do not use the recommended agents,  the following errors will be displayed:

  • PHOENIX 146 error for agent.
  • KeyError 101 error for CloudCache.

Network requirements

Field Requirement

Network Traffic rules

Phoenix agent:

Phoenix agents connect to Phoenix Cloud using port 443.

Phoenix CloudCache:  

Phoenix CloudCache connects to Phoenix Cloud using port 443.

Phoenix agents connect to Phoenix CloudCache using port 443. 

Phoenix Backup Store

 Phoenix Backup Store connects to the Phoenix Cloud using port 443.

Firewall  For all the agents and CloudCache: If the firewall is enabled, allow all outbound TCP/IP traffic to *.druva.com through port 443. 
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.

  • Was this article helpful?