The following Phoenix update is released for the cloud update on December 3, 2018:

With this cloud push, following enhancements to the MS SQL Server are available:

For more information, see:

Phoenix certifies backup and restore of databases that are created and managed using SQL Server 2017. For more information about the SQL Server 2017 support, see System requirements.

Action required: Upgrade the agent to the latest version.

The following Phoenix update is released for the cloud update on November 5, 2018:

Role Based Access Control (RBAC) enables organizations to limit privileged user access to a predefined set of administrator roles and data assets to create ethical walls and enforce privacy and control. RBAC also enables the implementation of a delegated administration structure to meet customers’ organizational, compliance, and security requirements. Thus, organizations can achieve their goals efficiently with a seamless, granular, extensible administrator role management of their entities.

The enhanced RBAC offers the following capabilities:

Action required: Upgrade the agent to the version 4.7.6 or later.

For more information, see Manage administrator roles.

Phoenix extends support for backup and restore of databases that are created and managed using SQL Server 2017. For more information about the SQL Server 2017 support, see System requirements.

Action required: Upgrade the agent to the version 4.7.6 or later.

Starting October 15, 2018, the agents use TLS 1.2 to interact with Cloud. Here's how it impacts you:

Action required: To use the agent that connects to the Cloud using TLS 1.2, upgrade it to the latest version.

The following Phoenix update is released with the cloud push on October 1, 2018:

With this cloud push, you can re-register a Hyper-V host. You may want to re-register a Hyper-V host if:

When you re-register a Hyper-V host, the snapshot chain of the virtual machines running on the host is not broken.

For more information, see re-register a Hyper-V host.

Action required: Upgrade the #######{{phoenix_agent}} to the latest available version.

The following Phoenix update is released for the cloud update on September 17, 2018:

With this cloud update, Phoenix extends its restore capabilities for SQL servers by introducing the following restore enhancements:

To restore the databases to an AG, ensure that you run the Phoenix service with the domain account.

For more information, see:

Action required: Upgrade the agent to the version 4.7.6 or later.

The following Phoenix updates are released with the cloud update on September 03, 2018:

With this release, #######{{phoenix_cloud}} will support TLS 1.2. Now, you will only be able to access the #######{{console}} using browsers that support TLS 1.2.

Phoenix agents that will support TLS 1.2 are scheduled for the upcoming major releases. Keep a track of the updates on this page to stay informed about the agent versions that will support TLS 1.2.

Action required: Use browsers that support TLS 1.2.

The Phoenix agent released with this cloud push can back up Hyper-V virtual machines hosted on Windows Server 2016 using the Resilient Change Tracking feature. For the Phoenix agent to use the Resilient Change Tracking (RCT) feature:

For more information, see:

Action required: If you are backing up Hyper-V virtual machines for the first time, ensure that you use the latest Phoenix agent. If you want to use RCT for Hyper-V virtual machines hosted on Windows Server 2016, upgrade the Phoenix agent on the host and change the backup method to RCT.

Note: With the introduction of support for Resilient Change Tracking (RCT), the Phoenix agent uses the native Hyper-V technology to back up the virtual machine files in RAW image format. Before the support of RCT, the Phoenix agent backed up the virtual machine files using the Volume Shadow Copy Service (VSS). With VSS, the Phoenix agent backed up the virtual machine files like flat files. With this change, you may not get deduplication savings for the two different file formats and the storage consumption may increase. However, there is no impact on the backup and restore jobs. You can use older snapshots created using VSS to restore virtual machines on the hosts. For more information, contact Support.

You can now back up and restore vApp virtual machines. You can restore a vApp virtual machine using the original location restore. However, restore to an alternate vApp location is not supported.

Action required: Update the Phoenix backup proxy to the latest revision.

The Phoenix agent attempts a secure connection to the MS-SQL servers hosted on Windows servers to back up databases. The secure connection to MS-SQL server happens through one of the following protocols:

If TLS 1.0 is disabled, and you are using TLS 1.1 or TLS 1.2 ensure that SQL Server Native Client driver 11.0 is installed. Since TLS 1.0 and TLS 1.1 protocols are getting deprecated, if the TLS 1.0 protocol is disabled, and you are using TLS 1.1 or TLS 1.2 and the SQL Server Native Client driver is not installed, the backup jobs fail on the Windows server.

You can download the SQL Server Native Client driver for the MS-SQL Server 2012 from the Microsoft Download Center.

The following Phoenix updates are released for the cloud update on August 06, 2018:

Now, when you restore a Hyper-V virtual machine to an alternate location, Phoenix provides you the option to select a network.

Action required: Upgrade the agent to the latest version.

The following Phoenix updates are released for the cloud update on July 16, 2018:

Phoenix can now back up VMware virtual machines hosted on vCenter 6.7 and ESXi 6.7. For more information on the VMware versions that Phoenix now supports, see System requirements.

Action required: Upgrade the backup proxy to the latest version.

You can now exclude virtual disks attached to a virtual machine while configuring it for backup.

For more information, see:

Action required: Upgrade the backup proxy to the latest version.

The following Phoenix updates are released for the cloud update on July 2nd, 2018:

Phoenix announces the general availability of the Druva Cloud Platform Console.

If you want to use the domain account credentials to back up the MS-SQL server databases, you can now provide the credentials at the time of installing the Phoenix agent.

Action required: Upgrade the agent to the latest version.

To use domain account credentials, ensure that you manually upgrade the Phoenix agent. To manually upgrade the Phoenix agent, download and install the latest Phoenix agent on the server, and provide the domain account credentials at the time of installing the Phoenix agent. Enter the domain account username in the format: domain\username.
If you are already using the domain user account credentials, the Phoenix agent loses the credentials if you auto upgrade the Phoenix agent, and the backup jobs fail.

The following Phoenix updates are released for the cloud update on June 04, 2018:

For an enhanced user experience, Druva is excited to announce the following changes:

For more information, see: Organization Dashboard

Customer action required: No action required.

Druva Phoenix now supports wildcard exclusion in File servers and NAS shares. With this feature, the Phoenix administrators can exclude certain files and folders from being backed up. This feature supports exclusions based on file paths, filenames, folder names, and folder paths. The file extension is considered as part of the filename.

The following wildcard support is available in the folder exclusion policy:

For more information, see:

Customer action required: No action required.

With this Cloud update, Phoenix no longer supports agents with version 3.4 and earlier. Ensure that you upgrade the Phoenix agents on your servers to the latest version to continue to back up and restore the servers.

For more information, see Phoenix EOL policy.

For an enhanced user experience, Druva is excited to announce the following changes with the Cloud update scheduled for June 04, 2018:

Customer action required: No action required.

This cloud update has minor backend changes and bug fixes.

This cloud update has minor backend changes and bug fixes.

Before you upgrade Phoenix agent on Windows 2008 server, ensure that Microsoft Visual C++ 2008 Redistributable package is installed.

The following Phoenix updates are released for the cloud update on April 16, 2018:

Druva is excited to announce support for File-level Restore (FLR) for Hyper-V virtual machines. With FLR, Phoenix administrators can recover individual files and folders on a virtual machine guest operating system from a backed up virtual machine. An administrator may need a file-level restore if:

For more information on Hyper-V FLR feature, see File-level restore (FLR) on virtual machines.

Action required: To use all the capabilities of this feature, Phoenix provides an FLR proxy for the Hyper-V virtual machine hosts. Deploy this proxy on the host to restore files from the backed up virtual machines.

Phoenix can now backup and restore virtual machines hosted on Windows Server 2008 R2.

For more information on certified versions, see System Requirements for Hyper-V.

Action required: Update the Phoenix agent to the latest version.

Phoenix now enables its administrators to set the pre-/post-backup script timeout period to a value greater than 2 hours.

The following table lists the issues fixed in this release.

The following Phoenix updates are released for the cloud update on April 02, 2018:

Druva is excited to introduce the following menu items in the Phoenix Management Console:

Audit trails enable organizations to meet data governance and compliance requirements by providing a chronological view of all administrator data activities. With Audit trail, Phoenix maintains the history of all the activities that the Phoenix administrators perform on the Phoenix Management Console. Cloud administrators can track and monitor all the activities ensuring complete transparency, traceability, and accountability of all the administrators and thereby aiding forensics and compliance initiatives.

Audit trail captures activity details, such as the name of the administrator who accessed the entity, the action performed, the resource and the entity on which the activity was performed, the timestamp of the action performed, and the updated values of the entity. After an activity is completed, there is no latency and Phoenix logs the audit details immediately without any interaction with the administrators.

The key features of this update enable cloud administrators to:

For more information, see:

Customer action required: No action required.

Phoenix now supports SQL instances that are configured under AlwaysOn Failover Cluster Instances (FCI) for instance-level high availability.

For more information, see:

Customer action required: No action required.

With Phoenix agent 4.7.1, the default settings to retain snapshots have changed. Earlier, you could use the pre-populated values in the retention settings of the backup policy (number of dailies, weeklies, monthlies, and yearlies). Now, the default values are removed, and Phoenix requires you to explicitly specify the retention values while creating a backup policy. This change does not impact the existing retention policies.

If you are registering a server under the Default Organization, Phoenix provides a default backup policy with the following retention settings:

Customer action required: No action required.

This cloud update had minor backend changes and bug fixes.

Druva is excited to announce the following features with the Cloud update scheduled for April 02, 2018:

With the aim to constantly enhance the user experience, Druva is excited to introduce the following menu items in the Phoenix Management Console:

Audit trails enable organizations to meet data governance and compliance requirements by providing a chronological view of all administrator data activities. With Audit trail, Phoenix maintains the history of all the activities that the Phoenix administrators perform on the Phoenix Management Console. Cloud administrators can track and monitor all the activities ensuring complete transparency, traceability, and accountability of all the administrators and thereby aiding forensics and compliance initiatives.

Audit trail captures activity details, such as the name of the administrator who accessed the entity, the action performed, the resource and the entity on which the activity was performed, the timestamp of the action performed, and the updated values of the entity. After an activity is completed, there is no latency and Phoenix logs the audit details immediately without any interaction with the administrators.

The key features of this update enable cloud administrators to:

Customer action required: No action required.

Phoenix now supports SQL instances that are configured under AlwaysOn Failover Cluster Instances (FCI) for instance-level high availability.

Customer action required: To use all the capabilities of this feature, upgrade to the Phoenix agent version that will be released with this Cloud update.

The following Phoenix update is released for the cloud update on March 5, 2018.

The expiry date information is no longer displayed in the License and Storage section of the Phoenix dashboard as shown in the following screenshots. This is done to align with the non-expiring nature of Phoenix credits.

The following Phoenix updates are released for the cloud update on February 05, 2018.

Druva now supports AlwaysOn Availability Groups for MS-SQL server. You can back up databases that are a part of the AlwaysOn Availability Groups for MS-SQL server.

The key features of this update include:

With this update, Phoenix provides a new menu option, Protect menu, and the Servers menu is moved to the Protect menu. To access the MS-SQL server backup and restore configurations, operations, and other listings, click Protect > MS-SQL Server.

Action required: To use all the new capabilities of this feature, upgrade to the Phoenix agent version 4.7.1.

You can now backup jobs through the command-line interface. The command line utility is supported only for the configured MS-SQL backup sets.

For more information, see Trigger backup using command-line interface.

Action required: To use the new capability of this feature, upgrade to the Phoenix agent version 4.7.1.

With this update, you can start using an AWS account with multiple Phoenix organizations for disaster recovery. Virtual machines from multiple organizations can be replicated to a single AWS virtual private cloud subnet.

For more information, see DRaaS FAQs.

You can select resource pool, folder, and network settings at the time of restoring a virtual machine or disk to an alternate location.

For more information, see:

To use this feature, upgrade to backup proxy version 4.7.1. Since the automatic upgrade to backup proxy version 4.7.1 is not supported, you must deploy the new backup proxy through OVA on the Downloads page.
See, Upgrade backup proxy.

The following issue is fixed with the Phoenix update released on Feb 05, 2018:

The following Phoenix updates are released for the cloud update on January 15, 2018.