Druva Phoenix FAQ

About Phoenix

Druva Phoenix is a cloud based backup and archival solution aimed primarily at remote office servers. Since Phoenix is cloud-targeted backup, there is no elaborate deployment needed to get started. All that is needed is an install of the Phoenix agent on servers that need to be backed up. Phoenix agents establish a connection between the servers and Phoenix cloud. After performing some quick configuration tasks from the Phoenix Management Console, Phoenix will start backing up data.

Phoenix backs up servers using Windows and Linux operating systems, as well as Microsoft SQL Server.

Supported Windows Versions:

  • Windows Server 2003 (32-bit / 64-bit)
  • Windows Server 2008 (64-bit)
  • Windows Server 2012 (64-bit)

Supported Linux Versions:

  • CentOS 6.x (64-bit)
  • Red Hat Enterprise Linux (RHEL) 6.x (64-bit)

Supported SQL Server Versions (Standard and Enterprise):

  • SQL Server 2008 SP4
  • SQL Server 2008 R2 SP3
  • SQL Server 2012 SP2
  • Built on the industry’s most comprehensive data security and privacy framework, an envelope key management model for encryption allow for complete data privacy under all circumstances without any key management required by the administrator.
  • Licensing is consumption based with a tiered pricing model. Both backup and archived data can be managed from a single dashboard, with data seamlessly moved to lower cost storage as it ages. Phoenix is a cloud-based, unified server backup and archiving solution. Built on the advanced cloud technologies offered by Amazon Web services, Phoenix promises best-in-class durability and infinite scalability for growing server data needs.
  • The powerful global deduplication that Phoenix employs ensures reduced backup windows and faster restores. With Phoenix, one can expect faster backups, with native server connections of up to 100Mbps. When deduplication is taken into account, effective speeds of up to 1Gbps can be seen.
  • The Phoenix CloudCache Server can further increase the speed and efficiency of both backups and restores. Ideal for those with extremely bandwidth challenged locations, or with very short RTO requirements, data of a determined time interval can be cached on an appliance close to the server. This allows for LAN speed backup and restore, with the ability to send this data to the cloud on a schedule that makes sense for your enterprise.
  • A Phoenix deployment is entirely cloud based. Free up existing IT staff from having to manage multi tier implementations with secondary storage locations, or increase the reliability of backups in offices that may not have appropriate levels of IT support.
  • The flexible design of Phoenix can be leveraged to support backup and restore needs of organizations of all sizes, from a single remote office file server to a globally distributed enterprise – all from a single console.

For the existing inSync customer, they will feel right at home with Phoenix. For those new to Druva’s backup technologies, they will be impressed with the ease of use and low administrative overhead.

  • Phoenix is a backup and restore solution for server data. In comparison, inSync is backup and restore solution for all endpoint devices, such as laptops, desktops, phones and tablets.
  • Phoenix is entirely in the cloud; an install and activation of a server agent is all that is needed to get started. inSync comes as two offerings – either cloud or on-premise.
  • Phoenix is designed for server data needs; data can be retained indefinitely, while permitting restores of data from any snapshot. Backups can happen at a faster rate, which is ideal for the larger amount of data and higher change rates of the average server, as compared to an endpoint device.
  • The administration console of Phoenix caters to server backup administrators, allowing for quick insights and the ability to manage server data. By contrast, inSync is designed for endpoint devices, the console caters to the backup and restore needs of modern users, recognizing that most employees work with corporate data across many devices.
  • Phoenix has been qualified at native backup speeds approaching 100Mbps. inSync is designed and connectivity is optimized to scale to 10s of thousands of connections with smaller workloads. Server workloads are larger, but the number of connections is lower. This allows for significant throughput differences for speeding up backup and restore processes.

Unlimited restores are included, there is never an additional cost to restore data.

Security and Certifications

Phoenix adheres to the same certifications as InSync. As an IaaS provider, Amazon regularly updates their compliance certifications for all the standard certifications. Further details are available and up to date here: http://aws.amazon.com/compliance/. As the SaaS provider, Druva holds a number of specific certifications related to how we control and manage our own applications. This includes an ISAE 3000 Type II audit performed yearly by KPMG, as well as a review of our security and privacy controls for handling HIPAA-compliant protected health information (PHI).

To ensure data stays protected, data is encrypted using 256-bit TLS encryption while in transit. At rest, Phoenix encrypts data using a unique 256-bit AES key for each customer. In addition to encryption, data scrambling techniques are used to further obscure access to data.

Yes, when provisioning a server the data can be scoped to server clusters within a specific geography (“availability zone”, as it is known within Amazon Web Services). This can provide complete assurance that data never leaves a specific geography.

Sizing and Setup

Storage consumption is displayed on the storage page ( Manage > Storages) in the admin console. The Storage Used column displays the total storage that is consumed across all servers. This is the ideal place to see storage utilization against purchased storage.

No, it will not. If all licensed storage is consumed, additional storage can be requested through the sales team. In the interim, server backups will function normally.


Data is backed up to Amazon Web Services, and is encrypted in transit and at rest. Phoenix leverages the robustness and the security standards of Amazon Web Services in conjunction with a unique architectural design to ensure the security of backup data.

The first backup of the server is a full backup, with deduplication of data across every server that has been previously backed up by a specific customer. Thereafter, every backup Phoenix performs is an incremental backup. This is known in the industry as “incremental forever”.

Druva Phoenix is designed for enterprise server backup, with enterprise level SLAs. Transfer rates of up to 100 Mbps per server are possible.

Phoenix uses a variable block size technique (based on file type) to determine globally duplicated data across all of a specific customer’s servers. The Phoenix agent only transfers unique blocks of data to the cloud. By doing this on the client side, massive bandwidth savings can be realized – up to 80% in many cases. This makes could backup a viable solution in locations where previously not possible.

Phoenix is designed to work efficiently even from sites with intermittent connectivity. If the Phoenix agent cannot reach Phoenix cloud, backups or restores stop temporarily. When the connectivity resumes, backups or restores start again. A single backup can therefore span multiple backup windows.

Phoenix CloudCache Server

Phoenix CloudCache Server​ is a dedicated virtual appliance that stores up to 30 days of backups locally (to enable quick local restores), and then periodically synchronizes this data to the Phoenix cloud. Since Phoenix agents communicate directly with CloudCache on a local network, the speed of backups and restores increases significantly, as they can be done at LAN speed. Moreover, administrators can schedule synchronization operations from Phoenix CloudCache Server​ to Phoenix Master during off-peak hours, thus ensuring an optimized utilization of WAN bandwidth.

With CloudCache, two main differences will be seen. The backup interval will reduce significantly as Phoenix agents backup data directly to CloudCache Server on the LAN. The data saved to CloudCache can be restored at any time during the pre-defined retention period directly from this local server. Local restores are faster, and they can be done at LAN speed. Additionally, data can be sent to the cloud during off hours, which is ideal for sites with limited available bandwidth.


Phoenix supports a flexible server administrator model, with the concept of a delegated administrator model if desired. These are admins who only have access to specific groups of servers. This is all controlled by Cloud Administrators, which have unrestricted access to the server. A deployment can have as many administrators as needed, but each environment should always have at least two Cloud Administrators at all times. If the credentials were lost for a single admin account, there would be no way to recover data from the system. This is by design, and ensures that only the customer has access to any data under any circumstance.

Group administrators manage a subset of servers within a deployment, with controlled access to the server groups to which they are associated. They have necessary permissions for server group activities such as managing backup policies, and managing servers belonging to their server groups. A group administrator can be assigned to manage multiple server groups. Similarly, a single server group can be managed by more than one group administrator.

Druva ©2020. All rights reserved. Privacy Policy

Linkedin twitter G+ facebook blog