Skip to main content

How can we help you?

Druva Documentation

System requirements

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


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

Note: The prerequisites for Phoenix CloudCache depend on factors such as the size of backup data and the number of backup sets that are mapped to the Phoenix CloudCache. To know the exact prerequisites for your setup, contact Druva Support (

Software requirements for Phoenix CloudCache  

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

Operating system



  • Windows Server 2012 R2 Standard Edition (64-bit)
  • Windows Server 2016 (64-bit)
Linux Linux CloudCache can be deployed using an OVA for vCenter.

Hardware requirements


Minimum Requirement



64-bit, quad-core processor


CPU 12



8 GB or greater


16 GB

Disk Space


1 TB data disk and 50 GB OS disk

Network Traffic rules

Outgoing network traffic: Phoenix CloudCache connects to Druva Cloud using port 443.
Incoming network traffic: Hybrid Workloads agents connect to Phoenix CloudCache using port 443.


If a firewall is enabled, allow all outgoing TCP/IP traffic to port 443 for "*". 

Web proxy Druva supports the following proxy types:
  • HTTP
  • socks4
  • socks5

For more information see:

 Note:  Druva 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.

Ports and communication protocols for Druva Phoenix

Phoenix CloudCache communicates with your servers and Druva 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 Druva 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.

CC_UXRefresh_Ports and Network.png

Deployment considerations

The optimum deployment for Phoenix CloudCache depends on the size and amount of activity that you expect your Druva Phoenix setup to handle. In most cases, we recommend that you analyze your organization’s needs to determine the aspects described in this section. 

Note: For assistance with setting up Phoenix CloudCache, contact the Druva Support

Licensing considerations

Phoenix CloudCache license comes bundled with the Enterprise and Elite editions.

Note: Phoenix CloudCache is not available for the Business edition.

Location considerations

Druva Phoenix recommends installing Phoenix CloudCache within the perimeter of each remote office location. A local installation of Phoenix CloudCache ensures that Hybrid Workloads agents can connect to Phoenix CloudCache through Local Area Network (LAN). This ensures faster backups and restores to and from Phoenix CloudCache. 

Note: In a production environment, we recommend that you configure one Phoenix CloudCache for each remote office location. 

Sizing and setup considerations

To ensure that Phoenix CloudCache can handle multiple backup and restore requests, you must set an optimum size for Phoenix CloudCache. You must also plan for the number of Phoenix CloudCache instances that you require at your remote office locations. 

The size of Phoenix CloudCache and the number of Phoenix CloudCache installations that you require depend on the factors, such as:

  • The number of servers that you want to back up.
  • The type of data backed up.
  • Size of the backup data (including incremental backups).

To know more about deployment considerations, contact Druva Support.

Resources considerations

The prerequisites for Phoenix CloudCache depend on factors, such as the size of backup data and the number of backup sets that are mapped to the Phoenix CloudCache. To know the exact prerequisites for your setup, contact Druva Support.

Note: In general, we recommend that in a production environment, you install Phoenix CloudCache on a dedicated server. 

Backup set mapping considerations

You can map one, multiple, or all the backup sets to a single instance of a Phoenix CloudCache. You can also choose a one-to-one mapping of the backup sets and the Phoenix CloudCache. 

The mapping approach that you choose depends on your organization's policies. We recommend that you ensure that your Phoenix CloudCache has sufficient storage to address the requirements of the assigned backup sets.