Skip to main content
Archived release notes and fixed issues 2018
Updated over 6 months ago

December 3, 2018

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

New Features

Ability to select different locations for MS SQL Server database files at the time of restore

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

  • You can now restore MDF, LDF, and NDF files to different locations.

  • You can now replace the database if you choose the Restore to original SQL Server Instance option.

For more information, see:

Certification of backup and restore of MS SQL Server 2017 databases

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.

Revision Information

Platform

Revision

Public Cloud

Gov Cloud

Windows

4.7.7-50491

Linux

Not Applicable

VMware backup proxy

Not Applicable

Hyper-V FLR proxy

Not Applicable

November 5, 2018

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

New Features

Enhanced Role Based Access Control

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:

  • New Roles tab on the Phoenix Management Console to optimize the role management of the entities by using roles and rights. A role defines the capability of an administrator and rights define the granular permissions assigned to the role, for example, Backup and Restore Management.

  • Seven predefined roles, which can be utilized to create various administrators to executes tasks effectively based on their organization's privacy or security needs.

  • Ability for the administrators to create new administrator roles from the three base administrator roles and customize their rights to the specific actions. For example, you can create a custom cloud administrator role to only back up devices but not restore them.

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

For more information, see Manage administrator roles.

Support for SQL Server 2017

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.

Fixed Issues

Issue

Description

ROBO-10531

Phoenix displayed an error message when the Phoenix administrator clicked the Druva cloud administrator’s name on the Administrators page.

ROBO-10470

Phoenix failed to create a Phoenix cloud administrator on the Druva Cloud Platform Console and displayed the following error message:

Error: Invalid operation. (#10000007f) (#100000001

ROBO-10561

The backup on the SQL Server 2008 standalone instance failed with the INTERNAL65535 error.

Revision Information

Platform

Revision

Public Cloud

Gov Cloud

Windows

4.7.6-48581

Linux

4.7.6-48581

VMware backup proxy

4.7.6-48581

Hyper-V FLR proxy

Not applicable

October 15, 2018

TLS 1.2 support on agents

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

  • Latest agents connect to the Phoenix Cloud using TLS 1.2. However, the older agents continue to use TLS 1.0.

  • Latest agents connect to the Phoenix CloudCache using TLS 1.2 if you have deployed a Phoenix CloudCache in your infrastructure. However, the older agents continue to use TLS 1.0.

  • Latest Phoenix CloudCache agent connects to the Phoenix Cloud using TLS 1.2 if you have deployed a Phoenix CloudCache in your infrastructure. However, the older Phoenix CloudCache agent continues to use TLS 1.0.

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

Fixed issues

Issue

Description

ROBO-10203

Backup activity shows a single entry for an availability group.

Revision Information (Agents)

Platform

Revision

Public Cloud

Gov Cloud

Windows

4.7.6-47047

Linux

4.7.6-47046

VMware backup proxy

4.7.6-47046

Hyper-V FLR proxy

4.7.6-47046

Revision Information (CloudCache)

Platform

Revision

Public Cloud

Gov Cloud

Windows

3.7-47047

October 1, 2018

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

Ability to re-register a Hyper-V host

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

  • You initially registered it as a standalone host, and you want to re-register the host as a part of a cluster or you want to re-register it as a host that is managed using System Center Virtual Machine Manager (SCVMM)

  • You initially registered a host that is a part of a cluster or it is managed using System Center Virtual Machine Manager (SCVMM), and you want to re-register it as a standalone host

  • You refreshed the hardware of the host and you want to replace the old host with the new one

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.

September 17, 2018

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

New Feature

SQL Availability Group Restore Enhancements

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

  • Provides the Automatic Seeding option on the Phoenix Management Console to initialize a secondary replica for SQL Server 2016 and later versions. Depending on your Always on Availability Group (AG) setup, you can now choose to replicate the database manually or automatically across the nodes in the AG.

  • Provides an ability to restore the database in the Recovery, No Recovery, or Standby mode after the SQL server database is restored using the snapshot or transaction log.

  • Provides an ability to add the restored database to a primary node or secondary node in the given AG. The database is restored and replicated across all the primary and secondary nodes in the AG.

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.

Fixed issues

Issue

Description

ROBO-10077

Volumes of a virtual machine are not displayed when an administrator attempts to run a file-level restore.

Revision Information

Platform

Revision

Public Cloud

Gov Cloud

Windows

4.7.6-46204

Linux

4.7.6-46125

VMware backup proxy

4.7.6-46154

Hyper-V FLR proxy

Not applicable

September 3, 2018

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

New Features

Support for TLS 1.2

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.

Support for backup of Hyper-V virtual machines using the Resilient Change Tracking (RCT) feature on Windows Server 2016 hosts

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:

  • The agent version must be 4.7.5 or later, and

  • The agent must be installed on a Windows Server 2016 with virtual machine configuration version 6.2 or later. If the virtual machine is hosted on a Hyper-V cluster, then the virtual machine cluster functional level must be level 9 or higher.

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.

Support for vApp virtual machines

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.

Revision Information

Platform

Revision

Public Cloud

Gov Cloud

Windows

4.7.5-45034

Linux

4.7.5-44922

VMware backup proxy

4.7.5-44922

Hyper-V FLR proxy

4.7.5-44922

August 20, 2018

Important information regarding MS-SQL Server backups and TLS 1.0 support

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:

  1. TLS 1.2

  2. TLS 1.1

  3. TLS 1.0

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.

Revision Information

Platform

Revision

Public Cloud

Gov Cloud

Windows

4.7.4-44325

Linux

4.7.4-44113

VMware backup proxy

4.7.4-44483

Hyper-V FLR proxy

NA

August 06, 2018

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

New Feature

Ability to select a network when you restore a Hyper-V virtual machine to an alternate location

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.

Revision Information

Platform

Revision

Public Cloud

Gov Cloud

Windows

4.7.4-43324

Linux

4.7.4-43077

VMware backup proxy

4.7.4-43077

Hyper-V FLR proxy

NA

July 16, 2018

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

New Features

Support for vCenter and ESXi 6.7

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.

Ability to exclude virtual disks at the time of configuring VMware virtual machines for backup

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.

Revision Information

Platform

Revision

Public Cloud

GovCloud

Windows

4.7.3-42851

Linux

4.7.3-42700

VMware backup proxy

4.7.3-42700

Hyper-V FLR proxy

4.7.3-42586

July 02, 2018

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

New Features

Druva Cloud Platform Console

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

Enhancement to the Phoenix agent for Windows

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.

Enhancement to Phoenix agent for Windows

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.

Fixed issues

Issue

Description

ROBO-9533

Backup jobs from the earlier versions of the Phoenix agent for SQL server databases were not listed on the Phoenix Management Console.

ROBO-9058

UI and emails had inconsistent report names.

Revision Information

Platform

Revision

Public Cloud

GovCloud

Windows

4.7.2-42106

Linux

4.7.2-42106

VMware Backup Proxy

4.7.2-42106

Hyper-V FLR Proxy

4.7.2-42125

June 04, 2018

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

New Features

Enhanced Jobs page

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

  • With the addition of the workload tabs to the Jobs page, Phoenix administrators can now simply click on the desired workload tabs to view the job details.

  • Druva has also enhanced the user experience for reporting. The Backup Activity and Restore Activity reports will now display details based on the workload types on the Manage Reports page.

For more information, see: Organization Dashboard

Customer action required: No action required.

Support for wildcard exclusion in File servers and NAS shares

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:

  • Wildcards without existing paths

    • Prefix (*abc): It excludes all the folders and files that end with “abc”.

    • Infix (*abc*): It excludes all the folders and files that contain the substring “abc”.

    • Postfix (abc*): It excludes all the folders and files that begin with “abc”.

  • Wildcards with existing paths

    • Prefix (Test/XYZ/*abc): The path must exist on the backup drive; otherwise, this wildcard exclusion is ignored. It excludes the folders and files that exist in the “Test/XYZ” folder and their names end with “abc”. This rule is applied only at given folder level.

    • Infix (Test/XYZ/*abc*): The path must exist on the backup drive; otherwise, this wildcard exclusion is ignored. It excludes the folders and files that exist in the “Test/XYZ” folder and their names contain “abc” as a substring. This rule is applied only at given folder level.

    • Postfix (Test/XYZ/abc*): The path must exist on the backup drive; otherwise, this wildcard exclusion is ignored. It excludes the folders and files that exist in the “Test/XYZ” folder and their names begin with “abc”. This rule is applied only at given folder level.

For more information, see:

Customer action required: No action required.

Other updates

  • In the Summary section of the Organization Dashboard, the integers that depict the latest backup status will no longer link to the Jobs page.

  • Phoenix has purged alerts related to the backup, restore, defreeze, and upload logs jobs. After the upgrade, the Alerts page and the Alerts History report will no longer display any existing alerts for backup, restore, defreeze, and upload logs jobs. However, Phoenix will continue to list the new alerts generated on the Alerts page.

Unsupported Phoenix agents

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.

Revision Information

Platform

Revision

Public Cloud

GovCloud

Windows

4.7.2-41524

Linux

4.7.2-41353

VMware Backup Proxy

4.7.2-41353

Hyper-V FLR Proxy

4.7.2-41353

Upcoming Phoenix Cloud update scheduled for June 04, 2018

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

  • With the addition of the workload tabs to the Jobs page, Phoenix administrators can now simply click on the desired workload tabs to view the job details.

  • Druva has also enhanced the user experience for reporting. The Backup Activity and Restore Activity reports will now display details based on the workload types on the Manage Reports page.

  • In the Summary section of the Organization Dashboard, the integers that depict the latest backup status, will no longer link to the Jobs page.

Customer action required: No action required.

May 21, 2018

This cloud update has minor backend changes and bug fixes.

Fixed issue

Issue

Description

ROBO-9168

Database not visible after a point-in-time restore.

May 07, 2018

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.

April 16, 2018

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

New Features

Support for Hyper-V File-level restore

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:

  • A file is accidentally deleted

  • A previous version of a file is needed

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.

Support for Windows Server 2008 R2 Hyper-V virtual machine hosts

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.

Extension of pre-/post-backup script timeout period

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

Fixed issues

The following table lists the issues fixed in this release.

Issue

Description

ROBO-8864

Phoenix UI: Console does not display more than 25 Cloud Cache Servers.

ROBO-8848

Change sys.availability_replicas to small case.

ROBO-8832

Unable to login into newly created Phoenix cloud instance.

ROBO-8829

The filter under Protect > File Backup Sets was broken.

ROBO-8271

VMware FLR: Add retry to vmware tool api in guest VM browse function.

ROBO-6709

File restore job runs into an error if the directory path ends with a blank space.

Revision Information

Platform

Revision

Public Cloud

GovCloud

Windows

4.7.1-39976

Linux

4.7.1-39976

VMware Backup Proxy

4.7.1-39976

Hyper-V FLR Proxy

4.7.1-39976

April 02, 2018

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

New Features

New menu items

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

Menu

Description

Manage

With the Manage menu, cloud administrators can now manage other Phoenix administrators and monitor their activities on the Phoenix Management Console.

The Administrators menu is now a submenu within the Manage menu.

To access the Administrator menu

On the menu bar, select All Organizations, and click Manage > Administrators.

Audit Trails

With the Audit Trails submenu, cloud administrators can now monitor and audit the activities that Phoenix administrators perform on the Phoenix Management Console.

For more information about Audit Trails, see Enhanced security with Audit Trail Reporting.

To access the Audit Trails menu

On the menu bar, select All Organizations, and click Manage > Audit Trails.

Reports

With the Reports menu, cloud administrators can now view and manage the Cost Allocation Report and the Admin Audit Trails Report.

To access the Reports menu

On the menu bar, select All Organizations, and click Reports.

Enhanced security with Audit Trail reporting

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:

  • Select resources and their specific entities for audit

  • Schedule and generate an Admin Audit Trails report

  • Audit the activity records for a maximum period of three years

For more information, see:

Customer action required: No action required.

Support for SQL Failover Cluster Instances

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.

Updated default retention settings

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:

  • All snapshots for: 14 days

  • Weekly revisions for: 4 weeks

  • Monthly revisions for: 3 months

  • Yearly revisions for: 3 years

Customer action required: No action required.

Revision Information

Platform

Revision

Public Cloud

GovCloud

Windows

4.7.1.39373

Linux

4.7.1.39373

Backup Proxy
Druva_Phoenix_Backup

4.7.1.39373

March 19, 2018

This cloud update had minor backend changes and bug fixes.

Upcoming Phoenix Cloud update scheduled for April 02, 2018

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

New menu items

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

Menu

Description

Manage

With the Manage menu, cloud administrators can now manage other Phoenix administrators and monitor their activities on the Phoenix Management Console.

The Administrators menu is now a submenu within the Manage menu.

To access the Administrator menu

On the menu bar, select All Organizations, and click Manage > Administrators.

Audit Trails

With the Audit Trails submenu, cloud administrators can now monitor and audit the activities that Phoenix administrators perform on the Phoenix Management Console.

For more information about Audit Trails, see Enhanced security with Audit Trail Reporting.

To access the Audit Trails menu

On the menu bar, select All Organizations, and click Manage > Audit Trails.

Reports

With the Reports menu, cloud administrators can now view and manage the Cost Allocation Report and the Admin Audit Trails Report.

To access the Reports menu

On the menu bar, select All Organizations, and click Reports.

Enhanced security with Audit Trail reporting

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:

  • Select resources and their specific entities for audit

  • Schedule and generate an Admin Audit Trails report

  • Audit the activity records for a maximum period of three years

Customer action required: No action required.

Support for SQL Failover Cluster Instances

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.

March 5, 2018

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

User Interface Update

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.

Revision Information

Platform

Revision

Public Cloud

GovCloud

Windows

4.7.1-38382

Linux

4.7.1-38397

Backup Proxy
Druva_Phoenix_Backup

4.7.1-38397

February 05, 2018

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

New Features

Support for AlwaysOn Availability Groups for MS-SQL server

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:

  • Seamless auto-discovery of MS-SQL instances and Availability Groups that are available on the MS-SQL server.

  • Ability to enable backups from any preferred secondary or primary node in the Availability Groups.

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.

Support to trigger backup using command-line interface

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

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

AWS account sharing across multiple organizations

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.

VMware enhancements

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.

Fixed Issues

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

  • ROBO-5865: Phoenix differential backup jobs for Filestream databases failed with an internal error. The full backup jobs and log backups completed successfully for these databases.

Revision Information

Platform

Revision

Public Cloud

GovCloud

Windows

4.7.1-37878

Linux

4.7.1-37878

Backup Proxy
Druva_Phoenix_Backup

4.7.1-37878

January 15, 2018

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

New Features

  • Phoenix now provides backup and restore for virtual machines created and managed using Hyper-V on Windows Server 2016

  • Support for Mumbai and UK regions

Revision Information

Platform

Revision

Public Cloud

GovCloud

Windows

4.7.0-37109

Linux

4.7.0-37109

Backup Proxy
Druva_Phoenix_Backup

4.7.0-37109

Did this answer your question?