Enterprise Workloads Editions: ✅ Business | ✅ Enterprise | ✅ Elite
This article contains three sections:
Software requirements for Oracle: Provides information about the Oracle database versions and the operating systems on the Oracle hosts that Druva certifies and supports.
Phoenix Backup Store system requirements: Provides information about the hardware and software required to set up a Phoenix Backup Store.
Ports and communication protocols for Druva: Provides information about the network configuration that the Phoenix Backup Store uses to connect to the Druva Cloud.
Software requirements for Oracle
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 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 |
|
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64-bit production |
|
📝 Notes
Druva for Oracle is not supported on non-English Oracle database editions and non-English operating systems.
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 |
|
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 |
|
📝 Note
Phoenix Backup Store does not support multi-node RAC setups if shared storage is not used for any of the data, control, or parameter files. Backup might fail in case any of these files are kept in the local storage of the nodes.
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 22.04 (64-bit) |
CPU | 8 Cores |
RAM | 8 GB |
Hard disks | At-least 300 GB. |
ZFS pool configuration | RAIDZ (Requires at-least three disks) |
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.x, 7.x, 8.x |
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.
Note: The configuration mentioned above is the default configuration. To backup an oracle database on PBS, make sure you have minimum 10% extra storage than the size of the database that you want to back up. If you want to back up multiple databases on the PBS, make sure the storage size is equal to or greater than the total size of the database that you want to back up. For example, to backup 4 databases each of size 2TB on PBS, then PBS must have minimum 9-10 TB storage allocated.
|
ZFS pool configuration | RAIDZ (Requires at-least three virtual disks) |
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 22.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) |
ZFS compression | LZ4 |
ZFS deduplication | Off |
ZFS record size | 128 KB |
Ports and communication protocols for Druva
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
Druva Cloud communicates with the Phoenix Backup Store to backup and restore data on it. To backup and restore data, the Druva Cloud communicates to the Phoenix Backup Store 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.
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.
📝 Note
If a firewall is set up, allow outbound TCP/IP traffic to *.druva.com through port 443.