Skip to main content
druva_logo.pngDruva
|
Documentation

How can we help you?

 

Trending articles:
Druva Documentation

Support matrix

  1. Last updated
  2. Save as PDF

Before you set up Druva, 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 Management Console.

Browser Minimum requirements

Web browser
  • Google Chrome 78
  • Microsoft Edge 92
  • Mozilla Firefox 70
  • Safari 14

Software requirements

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

Software requirements for files and folders

Druva 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 Druva 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 2022 (64-bit)
  • 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

(Standard and Enterprise editions)

 

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

 
  • Windows Server 2022 (64-bit)
  • 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,  7.6, 7.8 , and 8.3 (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, 7.6, 7.8, and 8.3 (64-bit)
  • Oracle Linux 6.8, 6.9, 6.10, 7.5, 7.6, 7.7, 7.8, 7.9 (64-bit)
  • SUSE Linux Enterprise Server (SLES) 11.4, 12.2, and 12.4 LTS (64-bit)
  • Amazon Linux 2

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

Note: Druva also supports the backup of files and folders on the non-VSS partitions such as FAT, FAT32, and exFAT. 

Ports and communication protocols for Druva 

Software requirements for Hyper-V

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

Operating System

Editions

Windows
  • Windows Server 2022 (Standard and Datacenter editions)
  • Windows Server 2019 (Standard and Datacenter editions)
  • 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)
Note: If you are using SCVMM for managing virtual machines on Windows Server 2008 R2 hosts:
  • When you activate the Hybrid Workloads 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.
  • Druva does not support registration of 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)

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 Druva 

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

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

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

Hyper-V_ports_and_ communication_protocols.png

 

Software requirements for MS-SQL server

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

Windows Server (64-bit)

(Standard and Enterprise editions)

SQL Server editions

Windows Server 2019
  • SQL Server 2019

Windows Server 2016 (x86-64)
  • SQL Server 2017
  • SQL Server 2016 SP1 
  • SQL Server 2014

Microsoft Windows Server 2012 R2
  • SQL Server 2017
  • 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 2017
  • 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

Note: Express editions are not supported.  

Prerequisites

  • The Hybrid Workloads agent interacts with Volume Shadow Copy Service (VSS) to perform full backups. Ensure that the Volume Shadow Copy Service is not disabled.

  • The Hybrid Workloads agent uses Microsoft SQL Server Virtual Device Interface (VDI) for differential and transaction log backups.

  • The account used for SQL backups and restores must also have the CREATE DATABASE permission for successful restores from snapshots. If the account used for SQL backups and restores does not have the CREATE DATABASE permission, the restores may fail with the SQL7 error. For more information, see GRANT Database Permissions.

Note: As with any other third-party backup software, Druva interfaces with Microsoft Virtual Device Interface (VDI) to perform differential and transaction log, backups and restores. The SysAdmin role is mandatory for VDI backups and restores. If the user account used for SQL VDI differential backups does not have the sysadmin role, the backups will fail in the initial stages.  If differential and transaction log backups and restores are not required, sysadmin permissions are not required. For more information, see  SQL Server VDI backup and restore operations require Sysadmin privileges.

  • Druva recommends that you use the Microsoft’s native VSS provider. If you are using a third-party VSS provider, you must configure Hybrid Workloads agents to recognize this provider. 

  • Ensure that the SQL Writer Service on your MS-SQL servers is running. 
  • Ensure that the disk space on the drive where your shadow copy storage is located is adequate for the cumulative size of your databases. To know how you can configure VSS to write shadow copies to a separate drive, see Set VSS to write shadow copies to a separate NTFS volume. 
  • Ensure that you enabled Windows authentication for your SQL servers. For more information, see Change Server Authentication Mode.  
  • Ensure that the Local System account has permissions listed in the following table:
    SQL privileges.png
    Permission Description
    Sysadmin Required for SQL server backup and restores. 

Note: As with any other third-party backup software, Druva interfaces with Microsoft Virtual Device Interface (VDI) to back up and restore SQL Database Transaction Logs. To use VDI, SysAdmin role is mandatory. If  transaction log backups and restores are not required, sysadmin permissions are not required.
For more information, see  Backup (Transact-SQL), and  Restore  Statements (Transact - SQL)

  • If you want to perform log backups for the database, ensure that you set the databases to FULL RECOVERY mode. For more information about modifying recovery mode, refer to View or Change the Recovery Model of a Database.  
  • Druva supports backup of availability group databases in MS-SQL server 2012 onward since Microsoft introduced availability group in SQL 2012.
  • Ensure that you install Hybrid Workloads agent on all primary and secondary nodes in the availability group.
  • Ensure that you enable the Readable secondary option for the secondary nodes for successful backups from that node.
  • Ensure that all the nodes in an availability group must have the same Hybrid Workloads agent version installed on them.
  • If you want the Hybrid Workloads agent to run under a domain user account:
    • Ensure that the domain user is added under the local administrative group of the SQL server
    • Ensure that Hybrid Workloads agent and SQL Server VSS writer service log on using the same domain user account. (By default both services log on using the local system account.)
    • Ensure that Sysadmin right is assigned to the domain user in the SQL server.

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. Druva can perform backup and restore provided your configuration adheres to the following  NAS proxy mappings.

Share type on the NAS device NAS device is mapped to Shares discovered
CIFS/SMB Windows NAS proxy CIFS/SMB
NFS Linux NAS proxy NFS
CIFS/SMB and NFS Windows NAS proxy CIFS/SMB
CIFS/SMB and NFS Linux NAS proxy NFS
CIFS/SMB and NFS Windows NAS proxy and Linux NAS proxy CIFS/SMB and NFS

Note: 

  • The NAS proxy must be version  4.8.16-98358 or later for share auto-discovery to work. 
  • Druva validates the NAS device credentials before adding the NAS device. Ensure that you have valid device credentials.
  • Druva supports Amazon FSx for Windows and Amazon EFS shares for backups and restores. You can protect Amazon FSx shares using a Windows proxy, and protect Amazon EFS shares using a Linux proxy.  For more information see Druva support for Amazon FSx for Windows and Amazon EFS
  • Druva supports Azure Files through SMB and NFS protocols via a NAS proxy. However, auto-discovery of shares is not supported as of now. For more information, see Add a NAS share.
  • Druva supports Nutanix Files through SMB and NFS protocols via a NAS proxy. For more information, see Add a NAS share.

Permissions for NAS auto-discovery

The IPC$ share must be accessible with the provided device credentials. Druva accesses this share to authenticate itself with the NAS device, after which it can discover the other shares on the device.

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 2022 (64-bit)
  • Windows Server 2019 (64-bit)
  • Windows Server 2016 R2 (64-bit) 
  • Windows Server 2012 R2 (64-bit) 
  • Windows Server 2008 R2 (64-bit) 

Druva 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, 7.6, 7.8, and 8.3 (64-bit)
  • Ubuntu 14.04, 16.04 , 18.04 LTS (64-bit), Ubuntu 20.04
  • 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, 7.6, ,7.8, and 8.3  (64-bit)
  • Oracle Linux 6.8, 6.9, 6.10, 7.5, 7.6, 7.7, 7.8, and 7.9 (64-bit)
  • SUSE Linux Enterprise Server (SLES) 11.4 and 12.2 (64-bit)
  • Amazon Linux 2

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

Ports and communication protocols for Druva 

Software requirements for Oracle Druva Backup Store

Druva supports the following Oracle instances:

Standalone instance

Oracle Database Versions

Host Operating Systems (64-bit)

Oracle Database 19c (19.3.0.0.0) - 64-bit production
  • Oracle Linux 7.x
  • Red Hat Enterprise Linux Server 7.x
  • Windows Server 2016
  • Windows Server 2019
Oracle Database 18c (18.3.0.0.0) - 64-bit production Oracle Linux 7.x

Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64-bit production
  • CentOS 7.x
  • Red Hat Enterprise Linux Server 7.x
  • Oracle Linux Server 7.x
  • Windows Server 2016
  • Windows Server 2019

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64-bit production
  • Red Hat Enterprise Linux Server 7.2-7.7
  • Red Hat Enterprise Linux Server 6.7
  • Oracle Linux Server 6.10
  • Windows Server 2012 R2 Standard Edition
  • Windows Server 2008 R2

Note: Druva can also back up and restore Oracle instances running on Solaris. For more information, contact Support. 

Real Application Cluster

Oracle Database Versions

Host Operating Systems (64-bit)

Oracle Database 19c (19.3.0.0.0) - 64-bit production
  • Red Hat Enterprise Linux Server 7.x
  • Oracle Linux Server 7.x

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

Oracle Linux Server 7.x

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64-bit production
  • CentOS 6.4 and later, 7.x
  • Oracle Linux Server 6.x, 7.x

Software requirements for Oracle Direct to Cloud

The following table lists the Oracle Database versions and the operating systems on the Oracle Server hosts that Druva supports:

Oracle Editions (64-bit) Oracle Linux Host (64-bit) Red Hat Enterprise Linux Server Host (64-bit) CentOS Host (64-bit)
Enterprise Editions
  • Oracle Database 19c Release
  • Oracle Database 18c Release
  • Oracle Database 12c Release
  • Oracle Linux 8.x UEK
  • Oracle Linux 7.x UEK
  • Oracle Linux 6.8 UEK 
  • RHEL 8.x
  • RHEL 7.x
  • RHEL 6.8 

CentOS 7.x
Standard Editions
Oracle Database 12c Release Oracle Linux 7.x UEK - CentOS 7.x
Oracle Database 18c Release - - CentOS 7.x

Note: Druva for Oracle is not supported on non-English Oracle database editions and non-English operating systems.

Software requirements for VMware  

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

vCenter Server

ESXi Host

 Backup Proxy Compatibility
7.0
  • 7.0
  • 6.7
  • 6.5
 4.8.15_96907

6.7
  • 6.7
  • 6.5
  • 6.0
 4.7.2-42700 or later

6.5
  • 6.5
  • 6.0
  • 5.5
  • 4.7.2-42700 or later
  • 4.6.9-27415 to 4.7.2-42106

6.0
  • 6.0
  • 5.5
  • 5.1
  • 4.7.2-42700 or later
  • 4.6.9-27415 to 4.7.2-42106

5.5
  • 5.5
  • 5.1
  • 4.7.2-42700 or later
  • 4.6.9-27415 to 4.7.2-42106
  • Druva does not certify VMware vCenter Server versions 5.5 and 5.1. However, backups and restores on these setups should work as expected.  Druva strongly recommends you to upgrade the VMware vCenter Server to the latest supported version. Refer to the article for more information about the end of the general support for vSphere 5.5.
  • Auto-upgrade will not be supported for proxies with versions less than 4.8.0. You must install the latest RPM manually. For more information, see Installing RPM for auto-upgrade.

 

Guest operating systems

Druva qualifies virtual machines with the following guest operating systems for backup. However, any guest operating system should work if the virtual machine snapshot(VMware tools quiescing turned ON) works fine. 

Operating System

Editions

Windows
  • Microsoft Windows Server 2019 (Standard, Datacenter)
  • Microsoft Windows Server 2016 (Standard, Datacenter)
  • Microsoft Windows Server 2012 R2 (Standard, Datacenter)
  • Microsoft Windows Server 2012 (Standard, Datacenter)
  • Microsoft Windows Server 2008 R2 (Standard, Datacenter)
Note: Druva performs image-level backups of virtual machines. So, unless you plan to enable application-aware processing for a virtual machine, Druva continues to back up the virtual machine with any guest operating system.

Linux
  • Red Hat Enterprise Linux (RHEL) 6.3, 6.9, 6.10 , 7.0 , 7.1-7.5
  • CentOS 5.3, 5.11, 6.3, 6.9, 6.10 ,  7.0 , 7.1-7.5
  • Ubuntu 14.04, 16.04
  • SUSE Linux Enterprise Server 11 SP 1 , 11 SP 4 , 12 , 12 SP 3 

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.)
    • Linux
      • MBR  (Simple/Spanned/Mirror/Striped) 
      • GPT (Simple/Spanned/Mirror/Striped)

File Systems
  • NTFS
  •  FAT
  •  FAT32 
  •  Ext2/3/4
  • XFS
  • Btrfs

File Type
  • Regular Files
  • Sparse Files
  • Hidden Files

OS, File System, and Volume types supported for Dynamic GPT

Item

Supported

Operating System

(source backup set)
 
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022

File Systems
  • NTFS
  • FAT
  • FAT32
  • *REFS

Volume Type
  • Simple
  • Striped
  • Spanned
  • Mirror
  • RAID-5

Note: For the REFS file system on any type of volume, the staging VM should be either the source backup set OS version or the next higher version for a successful browse and subsequent restore. For example, if the source backup set is Windows 2016, then the supported OS versions of the staging VM are 2016, 2019, and 2022.

vSAN versions

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

  • 7.0
  • 6.6
  • 6.5

Note: 

  • Phoenix backup proxy agent for VMware virtual infrastructure integrates with ESX and vSPhere vStorage API (VADP) to perform backup and restore.  

  • If the ESX/vSphere host is not licensed for the vStorage APIs, the backup and restore operations fail.

  • To verify whether the ESX/vSphere host is licensed for vStorage APIs - Click here

Installing RPM for auto-upgrade

Following are the steps to manually install RPM:

  1. Download RPM from Druva downloads page and copy the rpm on the backup proxy that needs to be upgraded.
  2. List the installed RPM name on your proxy using the following command:
    rpm -qa | grep druva
  3. Uninstall the RPM using the following command. Select No to prevent cleaning all the installation files.
    rpm -e <name from above command>
  4. Install RPM and start the Phoenix service:
    rpm -ivh <name of rpm copied from downloads page>
  5. Set the vCenter credentials on proxy using the following command:
    vCenterDetail set <hostfqdn> <username> <password>
  6. Restart the Phoenix service.
     

Guest operating systems

Druva qualifies virtual machines with the following guest operating systems for backup. However, any guest operating system should work if the virtual machine snapshot(VMware tools quiescing turned ON) works fine. 

Operating System

Editions

Windows
  • Microsoft Windows Server 2019 (Standard, Datacenter)
  • Microsoft Windows Server 2016 (Standard, Datacenter)
  • Microsoft Windows Server 2012 R2 (Standard, Datacenter)
  • Microsoft Windows Server 2012 (Standard, Datacenter)
  • Microsoft Windows Server 2008 R2 (Standard, Datacenter)
Note: Druva performs image-level backups of virtual machines. So, unless you plan to enable application-aware processing for a virtual machine, Druva continues to back up the virtual machine with any guest operating system.

Linux
  • Red Hat Enterprise Linux (RHEL) 6.3, 6.9, 6.10 , 7.0 , 7.1-7.5
  • CentOS 5.3, 5.11, 6.3, 6.9, 6.10 ,  7.0 , 7.1-7.5
  • Ubuntu 14.04, 16.04
  • SUSE Linux Enterprise Server 11 SP 1 , 11 SP 4 , 12 , 12 SP 3 

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.)
    • Linux
      • MBR  (Simple/Spanned/Mirror/Striped) 
      • GPT (Simple/Spanned/Mirror/Striped)

File Systems
  • NTFS
  •  FAT
  •  FAT32 
  •  Ext2/3/4
  • XFS
  • Btrfs

File Type
  • Regular Files
  • Sparse Files
  • Hidden Files

Software requirements for Nutanix AHV

Druva supports AHV as the underlying hypervisor. Druva supports all Long Term Support (LTS) and Short Term Support (STS) releases for AOS version 5.15 to AOS version 6.1. Druva does not support the Community Edition (CE) releases.

Druva supports all guest operating systems supported by Nutanix. For more information, see the Nutanix Compatibility Matrix.

Druva does not support the following disk types:

  • CDROM (the contents of CDROM aren’t backed up)
  • VMs containing volume groups (VG) Disks
     

Software requirements for CloudCache

Ports and communication protocols for Druva 

Hardware requirements

The Hybrid Workloads 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 Hybrid Workloads agent 

This section contains the prerequisites for the Hybrid Workloads agent. This configuration is applicable for one backup or restore job at a time. Applies to: 

  • Hyper-V virtual machines
  • Files on a server
  • MS-SQL server
Hardware requirements for installing Hybrid Workloads agent 
Hardware Minimum requirements

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 Druva application data. This application data is stored in the following locations:
    • Windows 2012 Server
      C:\ProgramData\Phoenix
    • Windows 2008 R2 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 Hybrid Workloads agent requires to run one backup or restore job at a time. By default, the Hybrid Workloads agent for NAS is configured to run six backup jobs in parallel.

Hardware

Minimum Requirement

CPU
  • Three Cores (per job) or,
  • Three vCPUs if the agent is installed on a virtual machine (per job)

RAM

3 GB (per job)

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

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. 

For more information, see Prerequisites to install the backup proxy.

Hardware requirements for the Druva 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

Note: Druva also supports  PBS deployment on the vCenter/ESXi version 7.0. For more details, contact Support.

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 32 GB
EBS Volume At-least 500 GB on a Throughput optimized GP2 (SSD). 
 
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 CloudCache

Prerequisite

Minimum Requirement

CPU

Windows

64-bit, quad-core processor

Linux

CPU 12

RAM

Windows

8 GB or greater

Linux

16 GB
Disk Space

Linux

1 TB data disk and 50 GB OS disk

Network Traffic rules

Outgoing network traffic: CloudCache connects to Druva Cloud using port 443.
Incoming network traffic: Hybrid Workloads agents connect to 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:  Druva does not support 4K native drives in the CloudCache environment. We recommend you to use 512 native drives for backup.    

To use 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

Hybrid Workloads agent:

Hybrid Workloads agents connect to Druva Cloud using port 443.

CloudCache:  

CloudCache connects to Druva Cloud using port 443.

Hybrid Workloads agents connect to CloudCache using port 443. 

Druva Backup Store

 Druva Backup Store connects to the Druva 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:
For more information, see Sizing for backup proxy.

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 Druva for their data protection solution.

Roles and responsibilities 

To prevent privileged users from making unauthorized changes to resources within their organization, Druva 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 Druva 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 , 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  

Druva supports SAML which allows organizations to centralized authentication for the administration of their Druva environment. This allows 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 Druva and eliminates local authentication stores which cause audit and compliance headaches as well as create a security risk. To integrate Druva with your SSO authentication mechanism, see Configure single sign-on for Druva.

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 Druva , contact Support.

Supported storage regions

The supported storage regions for Druva Cloud and Druva GovCloud are mentioned on the Cloud Status page of the Druva Support Portal. 

You can hover over the relevant donut chart on the Cloud Status page or click VIEW DETAILS to see the information.