Skip to main content
Druva Documentation

Release details

November 5, 2018

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

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

 

tick.png

 

tick.png

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 Phoenix agents

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

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

  • Latest Phoenix agents connect to the Phoenix CloudCache using TLS 1.2 if you have deployed a Phoenix CloudCache in your infrastructure. However, the older Phoenix 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 Phoenix agent that connect to the Phoenix 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 (Phoenix agent)

Platform Revision Public Cloud Gov Cloud
Windows 4.7.6-47047

 

tick.png

 

 

tick.png

 

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 tick.png tick.png

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.

  • Was this article helpful?