Skip to main content

 

Druva Documentation

System requirements

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

This article contains three sections:

Support matrix

This section provides information about the Oracle database versions and the operating systems on the Oracle hosts that Phoenix certifies and supports.

Support levels definition 

Druva categorizes its platform support levels as following:

  • 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 may provide support for such platforms, however, issues that require time and resources beyond commercial viability may not be addressed.

Certified Platforms

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

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

Supported Platforms 

Oracle Database Versions Host Operating Systems (64-bit)

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

Red Hat Enterprise Linux Server 6.7

System 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

Ports and communication protocols for Phoenix

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.