Skip to main content

 

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 server groups that are mapped to the Phoenix CloudCache. To know the exact prerequisites for your setup, contact Druva Support (support@druva.com).

System requirements 

Prerequisite Minimum Requirement
CPU 64-bit, quad-core processor
RAM 8 GB or greater
Operating system Windows Server 2012 R2 Standard Edition (64-bit)
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 Configure Web proxy.

 Note:  To use Phoenix CloudCache 3.3-7649 or later, you must have the following agents installed:

  • 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 above recommended agents,  the following errors will be displayed:

  • PHOENIX 146 error for agent.
  • KeyError 101 error for Cloud Cache.

Ports and communication protocols for Phoenix

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

Deployment considerations

The optimum deployment for Phoenix CloudCache depends on the size and amount of activity that you expect your 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 team (support@druva.com). 

Licensing considerations

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

Note: Phoenix CloudCache is not available for Business edition.

Location considerations

We recommend that you install Phoenix CloudCache within the perimeter of each remote office location. A local installation of Phoenix CloudCache ensures that Phoenix agents can connect to Phoenix CloudCache via 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 depends on factors such as:

  • The number of server groups (and hence the 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 (support@druva.com). 

Resources considerations

The prerequisites for Phoenix CloudCache depend on factors such as the size of backup data and the number of server groups that are mapped to the Phoenix CloudCache. To know the exact prerequisites for your setup, contact Druva Support (support@druva.com).

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

Server group mapping considerations

You can map one or multiple server groups to a single instance of Phoenix CloudCache. You can also choose a one-to-one mapping of server groups and Phoenix CloudCache. For more information about mapping server group, see Manage server groups.

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 servers groups.