Skip to main content

 

Druva Documentation

Release notes

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.
    Jobs.PNG

    |View larger image|

  • 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.
    Reports.PNG

    |View larger image|

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

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.

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                  
yes.png
                       
yes.png
Linux 4.7.1-39976
VMware Backup Proxy
Druva_Phoenix_Backup
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.

Administrator_menu.PNG

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.

Audit_Trails_menu.PNG

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.

Reports_menu.PNG

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

Known issues and workarounds

For more information on known and fixed issues, see Known issues and fixed issues.