Skip to main content
Druva Documentation

Archived release notes and fixed issues

Note: Refer to the "Revision information" table to know if the feature is available for Public Cloud/ GovCloud or both

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.

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.

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

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.

Old dashboard Latest dashboard

License_and_storage_old.JPG

|View larger image|

License_and_storage_new.png

|View larger image|

Revision Information
Platform Revision Public Cloud GovCloud

Windows

4.7.1-38382                  
yes.png
                       
yes.png
Linux 4.7.1-38397
Backup Proxy
Druva_Phoenix_Backup
4.7.1-38397February 05, 2018


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

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. To know more about how it impacts the current backup sets, click here.

For more information, see:

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.

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.

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                  
yes.png
                       
yes.png
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                  
yes.png
                       
yes.png
Linux 4.7.0-37109
Backup Proxy
Druva_Phoenix_Backup
4.7.0-37109

December 04, 2017

The following Phoenix updates are released for the cloud update on December 04, 2017.

Microsoft Hyper-V protection

Druva extends its virtual machine backup capabilities to Microsoft Hyper-V virtual machines. Phoenix Hyper-V agent resides on the Hyper-V host and performs image-level backups of the virtual machines. This eliminates the need to install the agent software on each virtual machine guest operating system. The key features include:

  • Forever incremental backups with source-side global deduplication.

  • Application consistent backups through integration with Microsoft VSS framework.

  • Support for all Hyper-V storage deployments including the local and cluster-shared volumes and SMB.

  • Flexible restore options, such as restore of the entire virtual machines or individual disks, and restore data to the original host or to an alternate host.

For more information, see Backup and Restore Hyper-V Virtual Machines.

NAS backup agent

Druva is pleased to announce a new approach for backing up Network Attached Storage (NAS) devices with Phoenix. The key highlights include:

  • Scale-out NAS agent that allows parallel and performant backups for large NAS deployments.
  • Smart scan approach, including machine learning through metadata analysis, that identifies data that has changed for backup versus initiating repeated backups of all data - changed or unchanged. By focusing on backup of only the new or changed data, backup cycles are dramatically shortened.  

  • Native data format and vendor agnostic approach that enables device migration and data intelligence use cases.

For more information, see Back up and restore NAS shares.

Support for Backup sets for physical servers

A backup set is a data set that you can configure for backups by defining the backup content and backup policies for files and databases. A backup set provides configuration options to customize the backup content, backup policy, and retention settings.

You can configure multiple data sets for backup with their own policies and settings, independent of each other. For example, if you want to back up files and MS-SQL server database on the same server, you can create two backup sets; one for files and another for the MS-SQL server database with their respective policies.

For more information, see:

Action required:

Upgrade to Phoenix agent version 4.7 to use all new capabilities of backup sets. 

Additional information:

To know more about what's changed with backup sets, check the article here.

For a quick demo of backup sets, check this video.

Support for Canada region

Druva now allows you to back up virtual machines in Canada. However, Druva does not support disaster recovery in this region.

Fixed Issues

The following issues are fixed with the Phoenix update released on Nov 20, 2017:

7592 Backup fails with INTERNAL65535 - TypeError: Incorrect padding
7507 CloudCache is not flushing data
7208 Disaster recovery request marked as failed in case of network retry scenario
6916 File Server backup fails with INTERNAL65535 - AttributeError: 'NoneType' object has no attribute 'get'
5672 Server status report shows different time zones for virtual machines although they are part of the same proxy pool
Revision Information
Platform Revision Public Cloud GovCloud
Windows 4.7.0-35567                                                                                                                                          
yes.png
                       
yes.png
Linux 4.7.0-35504
Backup Proxy
Druva_Phoenix_Backup
4.7.0-35504

October 16, 2017

Minor backend changes and bug-fixes. 

August 28, 2017

Following are the Phoenix updates released on August 21st, 2017.

New Feature

  • Age-based scanning under smart scan

    The Smart scan feature optimizes the scan duration during a backup job. Phoenix can save a lot of time if certain files and folders are not scanned at the time of backup. The Smart scan feature provides options that let you choose what should be skipped when Phoenix scans files and folders for backup. After you enable Smart scan, you can choose to skip files and folders that are not modified for a specified period of time, for example, 3 months. By default, the Smart scan option is disabled.

    You can enable this option while creating or editing a backup policy. For more information, see:

    For the frequently asked question about the Smart scan, see File server FAQs

Revision Information

Platform Revision Public Cloud GovCloud

Windows

4.6.12-32695                  
yes.png
                       
yes.png
Linux 4.6.12-32695
Backup Proxy
Druva_Phoenix_Backup
4.6.12-32695

July 17, 2017

Following are the Phoenix updates released on July 17, 2017.

New Features

  • Backup proxy pool selection
    Phoenix now lets you select a backup proxy pool at the time of restore. When you restore your virtual machine, virtual disk, or files, Phoenix provides an option to select a backup proxy pool. To ensure an enhanced restore performance, select a backup proxy pool with backup proxies that are locally connected to the destination hypervisor. 
    For more information, see:

    Action Required: No action required.

  • Two network interface cards
    The new Phoenix backup proxy now provides two network interface cards. After you deploy the new backup proxy, you can configure one network interface card for the public network and the other card for the private network. 

    Action Required: No action required.

  • Enhanced error reporting
    For backup and restore jobs that fail due to VMware reported errors, we have enhanced error reporting with details to better understand the failure causes.

    Action Required: No action required.

Revision Information

Platform Revision Public Cloud GovCloud

Windows

4.6.11-29892                  
yes.png
                       
yes.png
Linux 4.6.11-29892
Backup Proxy
Druva_Phoenix_Backup
4.6.11-29892

Note: To use the latest backup proxy, deploy it and add it to a backup proxy pool. You cannot upgrade existing backup proxy to the latest version using the Phoenix Management Console or RedHat Package Manager.

 July 3, 2017

Following are the Phoenix updates released on July 3, 2017.

New Features

  • Parallel scan and Smart scan
    Phoenix extends its backup capabilities for File server by introducing the following features:
     
    • Parallel scan: With the parallel scan feature, Phoenix agents scan files and upload data to the Phoenix cloud simultaneously. This feature ensures optimal utilization of the backup schedule window.

      For more information, see Overview of Phoenix for File server.

      Action Required: Upgrade the Phoenix agent to version 4.6.10 and later.
       
    • Smart scan:  The Smart scan feature optimizes the scanning duration for backup. To optimize the scanning duration, Smart scan excludes scanning of Access Control Lists (ACLs) for the files that are not modified since the last backup. 

      For more information, see Overview of Phoenix for File server.

      Action Required: Upgrade the Phoenix agent to version 4.6.10 and later.
       
  • Cost Allocation Reports
    Phoenix gives IT organizations the provision to chargeback to their internal groups for the credits consumed by their individual servers. It enables cloud administrators to categorize servers from one internal group into a logical cost object unit, such as server group and organization. Phoenix also introduces "cost code", an entity to map with server groups and organizations to determine the cost allocation of individual servers.

    Phoenix also provides a powerful cost allocation reporting mechanism to record credit consumption at each server level. The cost allocation reports enable cloud administrators to track the effectiveness of internal groups by retrieving credit usage details for individual servers and billing internal groups for the consumed storage. 

    Note: The Cost Allocation Report generated for July 2017 will include cost allocation details from July 3, 2017.

    For more information, see
  • In-product notification
    The in-product notifications are communications from Druva to the Phoenix administrators to keep them updated about the new features, product changes, and enhancements. In-product notifications are displayed under the  icon on the menu bar.

    There are 2 types of in-product notifications:

    • Informational notifications for a feature or an enhancement release. These notifications include links to release notes where administrators can read up further details.These notifications are represented with the  icon. Phoenix displays only one informational notification at a time.

    • Actionable notifications for actions that administrators must perform to prepare for the product updates. These notifications can be specific to all organizations or a single organization.

      These notifications are represented with the  icon. Phoenix displays up to four actionable notifications at a time. These notifications continue to show up until you perform the required action.

      For more information about in-product notification, see General FAQs.

       Action Required: No action required.

Revision Information

Platform Revision Public Cloud GovCloud
Windows 4.6.10-29131          yes.png          yes.png
Linux 4.6.10-29131
Backup Proxy
Druva_Phoenix_Backup
4.6.10-29131

May 16, 2017

Following are the Phoenix updates released on May 16, 2017.

New Features

  • Windows Server 2016 certification

    Phoenix now certifies File server agent on Windows Server 2016 (64-bit). 

    Action Required: To use Windows Server 2016 (64-bit) for physical hosts,  you will have to upgrade the File server agent to version 4.6.9 and later.
     
  • SQL Server 2016 certification

    Phoenix now certifies MS-SQL Server 2016 (64 bit). For more information about the certified versions, see Support matrix.

    Action Required: No action required.
     
  • Enhancement for VMware

    Phoenix now certifies vCenter 6.5 and ESXi 6.5. For more information about the certified versions for vCenter and ESXi, see Support matrix.

    Action Required
    • For new vCenter 6.5 and/or ESXi 6.5 setup registration: Deploy the Backup Proxy OVA version 4.6.9 or later.

    • For existing setup: Upgrade Backup Proxy to the rpm version 4.6.9 or later.

  • Enhancement for CloudCache 

    Phoenix now provides you with the ability to resize an existing CloudCache data volume. For more information about how to edit data volume size, see, see Edit data volumes.

    Action Required: No action required.

Fixed Issues

Following issue is fixed with the Phoenix update released on May 16, 2017:

  • ROBO-5750: Druva Install Package License Agreement shows incorrect schedule maintenance.  

Revision Information

Platform Revision Public Cloud GovCloud
Windows 4.6.9-27415                  yes.png
 
              yes.png         
 
Linux 4.6.9-27415
Backup Proxy
Druva_Phoenix_Backup
4.6.9-27415

May 15, 2017

The following is the Phoenix update released on May 15, 2017.

New Feature

User Interface Enhancements
Phoenix provides an intuitive, consistent, and improved first-user experience on the Phoenix Management Console.
The key UI enhancements include the following:

  • Site references on the Phoenix Management Console are renamed to Organization. Administrators generally associated the word site with geographical location instead of an access-based control mechanism for strict partitioning of entities such as servers, server groups, backup policies and so on, resulting in the incorrect configurations. To avoid location connotation that is associated with sites, Site is renamed to Organization as listed below:
    • Site is renamed to Organization 

    • Sites is renamed to Organizations

    • Site administrator is renamed to Organization administrator

    • All Sites in the main navigation menu bar is renamed to All Organizations

  • Improved Global and Organization dashboards

    The Summary tab on the Global and Organization dashboards has introduced the Total Snapshots field that provides statistics of the committed Restore Points. With a single-click on the statistics displayed on graphs and maps, you can now view detailed configuration information about servers, virtual machines, and so on. You no longer need to navigate through multiple pages to view configuration details.
  • Enhanced first-time landing pages for Organization, Servers, VMware, CloudCache, and Disaster Recovery

    These first-time landing pages now display enhanced workflow diagrams to help you understand the Phoenix components.
  • You can now sort jobs, configured servers, configured virtual machines, and alerts based on job ID, start time, job status, last backup status, and so on.

  • You can now hover on the error codes on the Jobs page and directly view error messages.

    Action Required: No action required.

April 17, 2017 

Following are the Phoenix updates released on April 17, 2017.

New Feature

  • File Server restore improvements

    With this new feature, Phoenix extends its restore capabilities for servers by introducing the following restore enhancements:

    • Allows backup and restore jobs to run simultaneously on the server. Earlier, restore job was queued if a backup job was in progress on the target server.
    • Provides the following new restore options:
      • Always overwrite
      • Always skip
      • Overwrite if original is older
      • Restore and move original to .orig
    • Provides the Preserve upward tree path option to retain the parent folders while restoring files to an alternate location.

Action Required: This feature is available only if you upgrade the File server agent to version 4.6.9 and later.

For more information about restore enhancements, see:

With this new feature, Phoenix extends its restore capabilities for virtual machines by introducing the following restore enhancements:

  • Provides an ability to perform File Level restore to a virtual machine.
  • Provides information about the volumes that could not be mounted during File Level restore.
  • Provides the following new restore options for File Level restore to a  virtual machine:
    • Always overwrite
    • Always skip
    • Overwrite if original is older
    • Restore and move original to .orig
  • Provides the Preserve upward tree path option to retain the parent folders while restoring files to an alternate location.
  • Allows you to cancel the ongoing backup job and trigger a restore request while restoring the virtual machine to an original location.

Action Required: This feature is available only if you upgrade the Backup Proxy to version 4.6.9 and later.

For more information about restore enhancements, see:

Phoenix certifies the following CentOS operating system versions:

  • CentOS 6.5
  • CentOS 6.6
  • CentOS 6.7
  • CentOS 6.8
  • CentOS 7.3

Phoenix certifies the following RHEL operating system versions: 

  • RHEL 6.5
  • RHEL 6.6
  • RHEl 6.7
  • RHEL 6.8
  • RHEL 7.3

For more information about the supported versions of CentOS and RHEL, see Support Matrix.

Action Required: No action required.

  • Pre-backup and post-backup scripts

Phoenix allows you to configure File Server agents to execute custom user scripts before and after a backup job.

You can configure Backup Policy with the settings for pre-backup and post-backup scripts to perform custom tasks, for example, to backup database dumps as flat files using the Phoenix File server agent and delete the dump files after the Phoenix backup job completes.

Action Required: Upgrade to File Server agent version 4.6.9 and later.

For more information, see: 

Fixed Issues

Following issues are fixed with the Phoenix update released on April 17, 2017:

  • ROBO-5757: CloudCache schedules ran outside defined window that spanned over multiple days with certain network disconnect and reconnect states.
  • ROBO-5780: Could not assign static IP address to a new Backup Proxy.

Revision information

Platform Revision Public Cloud GovCloud

Windows

4.6.9-21173                  yes.png
 
              yes.png         
 
Linux 4.6.9-21192
Backup Proxy
Druva_Phoenix_Backup
4.6.9-21192

April 03, 2017

Following are the Phoenix updates released on April 03, 2017.

New Feature

  • Credit Reporting

    Phoenix introduces "Credits" to extend its consumption-based pricing capabilities. It allows you to pre-purchase Phoenix storage using credits and in effect pay only for the storage that you consume. Phoenix Dashboard lets you track credits and storage consumption using various credits and consumption-related graphs. Phoenix credits are not applicable to customers onboarded through the AWS Marketplace. No credits-related information will be available to these customers on the Phoenix Admin console.

    Action Required: No action required.

    For more information, see: 
  • Phoenix Credits
  • Dashboard
  • View Storage and Storage details
  • Licensing consideration
     
  • Backup Proxy upgrade to CentOS 7

    Backup Proxy is now upgraded to CentOS 7.  This Backup Proxy additionally supports Extended File System (XFS) and uses the VDDK 6.0.2 library. 

    Impact: The auto upgrade Backup Proxy functionality will not work.

    Action Required: You must deploy the latest Backup Proxy OVA version 4.6.8 or later.
     
  • Backup and Restore of Empty Folders

    With this new feature, Phoenix has the ability to backup and restore empty folders on a File server.

       Action Required

  • Upgrade the File server agent to version 4.6.8 or later.
  • To back up empty folder created before the client upgrade on the Window File server, contact Druva Support.

      For more information, see: 

  • About File server backup
  • About File server restore
     
  • Error code hyperlink redirection

    For seamless user experience,  the error code hyperlink on Phoenix portal will redirect you to the exact error message description on the documentation portal.

    Action Required: No action required.
     
  • SSL enhancement

    The Phoenix physical server agent for Linux and Backup Proxy is updated with Open SSL 1.0.2j library to provide better protection against security vulnerabilities.

    Action Required: You must deploy the latest Backup Proxy version 4.6.8 or later.

Revision Information

Platform Revision Public Cloud GovCloud
Windows 4.6.8-20739                  yes.png                         yes.png
Linux

4.6.8-20739

Backup Proxy
Druva_Phoenix_Backup
4.6.8-20739

March 6, 2017

Automatically configure virtual machines for backup

With this new feature, Phoenix administrators can now create rules to automatically configure virtual machines for backup. This feature is available only if you have deployed the backup proxy version 4.6.7 or later on your vCenter setups.

Automatic configuration rules let you:

  • Specify server group
  • Specify backup proxy pool
  • Exclude VMs from getting automatically configured

The configuration rules that you create are applied to all the folders under vCenter. New virtual machines created under this folder are automatically configured for backup.

For more information, see:

Action required:  Upgrade Phoenix backup proxy to version 4.6.7 or above.

Fixed Issues

Following issues are fixed with the Phoenix update released on March 6, 2017

  • ROBO-4267: Remove infinite retries from agent upgrade.
  • ROBO-5135: File Server restore fails with 'E_ABSOLUTE_AND_NORMALIZED_PATH_LENGHT_MISMATCH'.
  • ROBO-5138: SQL Backup shows incorrect information about data scanned.
  • ROBO-5234: Phoenix agent process enters standby state and subsequent backup jobs are skipped. Phoenix server now runs a check every 15 minutes to ensure that the agent is not standing by. If it is, the agent process is restarted.
  • ROBO-5271: Customers with storage names having non ASCII unicode characters get an error when storage regions graph is rendered in global dashboard.
  • ROBO-5285: Enable (full and differential) SQL backup-restore support on windows 2003 server.
  • ROBO-5323: Unmap other mapped drives if process exits execution on abort.

Known Issue

Revision information

Platform Revision Public Cloud GovCloud

Windows

4.6.7-10428

                 yes.png
 
                        yes.png
 
Linux 4.6.7-10212
Backup Proxy
Druva_Phoenix_Backup
4.6.7-10212

February 20, 2017

Following are the Phoenix updates released on February 20, 2017.

Restriction on retention policy removed

Earlier, Phoenix disabled certain retention settings based on the retention period you specified for your daily, weekly, or monthly snapshots. For example, when you specified more than 365 days as retention period for daily snapshots, Phoenix disabled retention settings for weekly, monthly, and yearly revisions. This restriction on retention policy is now removed. 

Now, you can specify:

  • More than 365 days as retention period for daily snapshots
  • More than 52 weeks for weekly revisions
  • More than 12 months for monthly revisions

For more information, see Retention period under Key Concepts and Terms. 

February 6, 2017

Following are the Phoenix updates released on February 6, 2017.

New Feature:

  • SUSE Linux Enterprise Server (SLES) File Server support

    Phoenix extends its capability for file server backup to support SLES platform. Phoenix supports the following SLES operating system versions: 
    • SLES 11.4 (64-bit)
    • SLES 12.2 (64-bit)
      The SLES versions are supported platforms only. 

Action Required: Download the Linux agent from the Phoenix download page. 

For more information, see: 

  • UX Enhancements

    Phoenix provides a re-designed user interface to enable you to configure and manage Phoenix seamlessly.  The UI enhancements include text font change, improved button styling, uniform text alignment, and so on.

Revision information

Platform Revision Public Cloud GovCloud

Windows

NA

                 yes.png
 
                        yes.png
 
Linux 4.6.6-9938
Backup Proxy
Druva_Phoenix_Backup

4.6.6-9938

January 16, 2017

Following are the Phoenix updates released on January 16, 2017.

New Features:

  • Point-in-time restore using transaction log
    Updated SQL Server agent now supports transaction log backups. Transaction log continuously records changes to a database and provides a lightweight solution to back up and restore for databases that are updated frequently. Phoenix backs up transaction logs at regular specified intervals after a full or differential backup job is successfully completed. When you trigger a point-in-time restore job:
    • Phoenix picks the restore point created from the last successfully completed full or differential backup job, and
    • Phoenix uses the backed up transaction log to restore the database up to a transaction that is closest to the date and time you specify. The closest transaction can be the transaction that occurred right before the date and time you specify, or if exists, the transaction that occurred at the specified date and time. 
  • Transaction mark restore
    If you mark a transaction in SQL Server, you can use it to restore your database. Phoenix lets you choose a marked transaction to perform a point-in-time restore. The marked transaction restore, like the point-in-time restore using log backup, lets you restore your databases to a consistent state till a particular transaction occurs that updates your databases.

    In addition, Phoenix supports log truncation. Logs are truncated after Phoenix backs them up.
    Log backups are retained based on daily retention policy and are deleted if a log backup falls out of daily retention period. Weekly, monthly, and yearly backup policies are not applicable for log backups. For more information, see:
  • Action Required: To use this feature, upgrade to Phoenix client 4.6.6 and above.  

Fixed Issues:

Following issues are fixed with the Phoenix update released on January 16, 2017:

  • ROBO-4813: If a backup set is disabled and its policy is detached from the group of the client, the backup set should get deleted.

Revision information

Platform Revision Public Cloud GovCloud

Windows

 4.6.6-9617

                 yes.png
 
                        yes.png
 
Linux NA
Backup Proxy
Druva_Phoenix_Backup

NA

January 2, 2017

The following table lists the Phoenix updates released on January 2, 2017.

Fixed Issues
  • ROBO-4819: Decommission did not work for CloudCache that communicated with Phoenix Cloud through Web proxy.
  • ROBO-4653: During sync-up between CloudCache and Phoenix Cloud, CloudCache exceeded the bandwidth limit specified in the policy.

December 19, 2016

The following table lists the Phoenix updates released on December 19, 2016.

Feature Description Documentation Links
File Backup and Restore in Deduplication-enabled Volume

Phoenix supports backup and restore of data deduplication-enabled volumes on Windows 2012 File Server.

Action Required: To enable this feature, upgrade to Phoenix client version 4.6.5 and above.

NA
Non-admin Email Subscription

Non-Phoenix administrators can now subscribe to receive email notifications for alerts or reports. This feature helps various stakeholders within an organization to have access to job failure alerts or any other key reports.

Action Required: None.

Ubuntu File Server agent

Phoenix now extends its capability for File Server backup to support Ubuntu platform. Phoenix certifies the following Ubuntu OS versions:

  • Ubuntu 14.04 (64 bit)
  • Ubuntu 16.04 (64 bit)

Action Required: Download the Ubuntu agent from Phoenix download page.

Support matrix
Access Control Lists (ACL) support for Windows

File server now restores all Access Control Lists (ACL’s) that are associated with the files being restored.

Action Required: None.

Restore Phoenix File Server Agent

December 5, 2016

The following table lists the Phoenix updates released on December 5, 2016.

Feature Description Documentation Links
Single Sign-On

Phoenix now supports Single Sign-On (SSO) access. Administrators no longer require a separate login for Phoenix console, and can access using the SSO tool as implemented in their organization.

Phoenix supports all IdP tools that support SAML 2.0. Druva has tested and certified Active Directory Federation Services (ADFS) and Okta.

Action Required: To enable this feature, configure SSO on Phoenix and Identity Provider (IdP) portal.

 

Instrumentation 

Phoenix provides additional statistics for backup and restore jobs for VM, File Server, and MS-SQL Server. These instrumentation statistics provide additional information for data estimation, data transfer, and network environment, such as number of network retries, number of files transferred, file size distribution, network retry duration, and so on. These details provide more visibility into what is happening at the job level. It also facilitates faster troubleshooting when a backup or restore job runs for a longer duration than expected.  

Action Required: To enable this feature, upgrade to Phoenix client version 4.6.4 and above.

Job Enhancements

First Backup Behavior

Backup policy now includes an option to Ignore backup duration for first backup. Typically, the first backup job requires a lot of time due to a large data set getting backed up, and sometimes a specified duration is not enough.

By default, the Ignore backup duration for first backup option is enabled so that the first backup job ignores the specified backup duration. You can choose to disable this option from the backup policy to enforce backup duration for first backup.

Action Required: None.

New Backup Window Expired state for jobs

For jobs in which the specified backup duration was not enough for the entire data set to get backed up, a new state, Backup Window Expired, is now introduced. Users can ignore the message as the backup resumes when the next schedule kicks in.

Action required: None.

Previous Cloud push updates:

Feature Description Learn more
AWS SaaS Marketplace

AWS SaaS Marketplace is a new initiative by AWS for SaaS applications, such as Phoenix. It allows AWS customers to find Phoenix "Business" and "Enterprise" edition SKUs directly from the AWS SaaS Marketplace and purchase the SKUs on Druva's Web site. It benefits Phoenix with a better sales channel to reach out globally at a much lower customer acquisition cost compared to direct sales.

NA
Disaster Recovery Failover Automation

Disaster Recovery Failover Automation extends the Phoenix Disaster Recovery functionality by providing the ability to perform failover as a single-click operation. This feature introduces the concept of the Disaster Recovery (DR) Plan that encompasses the virtual machines configured for disaster recovery, the AWS account used for disaster recovery, the AMI update frequency, the network, security and instance-related failover settings, such as VPC, subnet, IP addresses, security group, and instance type. Preconfiguration of these settings in the DR Plan allows for a single-click failover in the event of a disaster.

With the introduction of the DR Plan, the DR Policy concept has been deprecated.

Action Required: Upgrade DR proxy to version 4.6.3 or above.

Global Dashboard

To provide administrators an overall summary of what's happening at the overall site level, Phoenix introduces a new Global Dashboard. The Global Dashboard  provides a summary of the consolidated physical server and virtual machines deployment and storage usage across all sites. In addition, the Site Dashboard is re-designed for an enhanced user experience.

Global Dashboard:

From the Phoenix Global dashboard, you can now view the following information:

  1. Summary:
    • Deployment status of configured and unconfigured servers, VMs, and CloudCache across sites.
    • Number of successful restores till date across sites.
    • Last backup status for all servers and VMs across sites.
    • Backup job status for the last seven days.
  2. Sites:
    • List of all sites in your environment with the details of the last backup status for all servers and VMs deployed in each site.
  3. Storage
    • Savings in the current Phoenix storage consumption as against the estimated traditional backup consumption, thereby, highlighting the patented Global Deduplication technology.
    • Increase in the source data from the first backup to the latest backup.
    • Phoenix storage usage in the last 90 days.
  4. Storage Regions:
    Displays the Phoenix storage used for a particular storage region. 
Site Dashboard

The Site dashboard provides the following information:

  1. Summary
    • Deployment status of configured and unconfigured servers, VMs,and CloudCache for the selected site.
    • Number of successful restores till date for the selected site.
    • Last backup status of all servers and VMs for the selected site.
    • Backup job status for the last seven days.
  2. Recent Alerts
    Shows the latest alerts for the selected site. 
  3. Backup Data
    Graphical representation of Source+Change and Current Source data in the last 90 days.
  4. Storage Region
    Displays the Phoenix storage used for all servers and VMs for the selected site. 

Action Required: None.

Storage reporting changes

The Phoenix storage reporting terms have been renamed with an enhanced graphical representation for easy access. The following table describes the changes:

New term Old term Definition
Phoenix storage Storage Used Phoenix Cloud storage consumed post deduplication.
Source+Change Ever Incremental data Amount of total backup data generated at source for all available snapshots.
Current Source Last Backup size Size of data on source servers as of last Backup.
Source Reduction Factor Global Deduplication saving Ratio of Source+Change to Phoenix Storage.
Global Deduplication saving Total Storage saving Ratio of Traditional Backup storage to Phoenix storage.

Action Required: None.

Proxy Load Balancing

With the Proxy Load Balancing feature, Phoenix introduces Backup Proxy pools. Backup Proxy pool is a collection of Backup proxies that are configured with a virtual machine for optimal load balancing. 

Action Required:

  • To enable this feature, upgrade all the Backup proxy client in your registered vCenter to version 4.6.2 and above.
  • After upgrading, it is recommended to refresh VM listing for each vCenter for the load balancer algorithm to function as expected. 
Job Improvements

The following Job enhancements are added as part of job improvements functionality:

  • Skipped job - A new job state 'skipped' is added. Any job that did not start within the scheduled window because another job is in progress will be marked as "skipped" on the job details page. 
  • Disconnected agent - Introduced a new error code PHOENIX 17 that will be displayed if a job is not triggered as the agent is disconnected from the Phoenix cloud.

Action Required: None.

Backup for server with mixed workload (Backup Sets)

This feature allows you to back up a single server that runs mixed workloads of File Server (Windows) and MS-SQL Database Server. Phoenix creates different restore points for the File and SQL workloads. However, you can currently define only one retention policy across the two workloads.

Action Required: None.

Job Based Logs

With the Job Based Logs feature, you can request and download the detailed logs for a particular job from the Job Details screen.

Action Required: To enable this feature, upgrade to Phoenix client version 4.6 and above.

Agent upgrades through Phoenix portal

This feature provides an easy way to upgrade agents to the latest versions from the Phoenix portal with a single button click. 

Action Required: Agent upgrade through Phoenix portal is supported from version 4.5 and above. You must manually upgrade to version 4.5 from the existing version.

VMware Performance Optimization

A series of performance enhancements have been added to the VMware agent resulting in higher performance for VM backups. With these enhancements, the recommended CPU and RAM configurations per job for the Backup Proxy have been revised. The default configuration for Backup Proxy has been revised to 8 vCPUs and 6 GB RAM from the previous configuration of 6 vCPUs and 6 GB RAM.

Impact: Improved VMware backup performance.

Action Required

  • For the existing Backup Proxies, the number of VM backups that can occur concurrently will need to be adjusted post upgrade in order to avoid any impact on Backup Proxy CPU utilization. For more details, please contact Druva Support for the next course of action. 
  • You must upgrade the DR proxy to the latest RPM version 4.4-r6780 to avoid any impact on DR restore. For more information, see the Downloads page.
Sizing for Backup Proxy
Changed Block Tracking

The Auto-enable CBT feature provides a way to automatically enable Changed Block Tracking (CBT) 
for configured VM(s) through Phoenix instead of an administrator doing it manually. The CBT setting is part of Backup Policy. Phoenix will try to enable CBT before the backup schedule kicks in for VM(s). There should be no user snapshots on the VM for the Auto-enable CBT to work. In case there are user snapshots on the VM, Phoenix will run a full scan to read the changed blocks.

Impact: Enhanced incremental backup performance. 

Action Required: You must upgrade to Phoenix Backup proxy version 4.4 or above.

 

VMware Tools Quiescing

Enable or disable VMware tools quiescing if they are installed on the system. The quiescence setting is part of Backup Policy. If enabled, Phoenix will take an application consistent snapshot. If disabled or VMware tools not installed or running, the backup will still take a crash-consistent snapshot.

Impact: Disabling quiescing will ensure backup will still run, incase of an issue with the VMware tools or in case of VSS service not running.

Action Required: You must upgrade to Phoenix Backup proxy version 4.4 or above

Backup Proxy replacement

Backup Proxy Replacement provides an effective way to replace an existing Backup Proxy with a new one. This is typically required in a situation where an administrator deploys a new Backup Proxy to take advantage of VMware FLR capabilities or a better performance proxy. The replacement workflow also ensures that all VM(s) mapped to the old proxy are reconfigured to the new proxy ensuring a smooth transition for a VMware admin.

Impact:  Single workflow to reconfigure bulk VM(s) and delete the older proxy resulting in better usability.

Action Required: None.

Replace Backup Proxy

CloudCache True Hot Restore

The CloudCache True Hot Restore feature will ensure all the dedupe data from Server group(s) is retained locally on the CloudCache for the pre- defined retention period.

Impact: This feature will result in faster data restore from CloudCache in case of bandwidth constrained sites. If you want to store all data locally, detach and attach the server group to the CloudCache. This will result in a one-time full backup to the CloudCache. During the first full backup, there may be a longer backup window.

Action Required: You must upgrade to Phoenix agent version 4.3 or above and CloudCache version 3.1 or above.

Phoenix True Hot Restore
Performance Improvements

Architectural optimization for better backup performance in File server, SQL server, and UNC share.

Impact: Enhanced backup performance.

Action Required: You must upgrade to Phoenix agent version 4.3 or above.

 
Storage Reporting

Phoenix now highlights the patented Global Deduplication Technology.  This provides you with the best storage optimization in the industry.  The transition from “Ever Incremental” to “Phoenix” storage highlights a new innovation in Server Storage, giving you more availability and control over your storage.

Impact:

  • With this release, we have updated the storage pages, server and server group pages with a number of  useful storage related statistics. These statistics will help you to gain more visibility on the storage savings achieved with Phoenix.
  • The storage page is updated to show comparative picture of storage consumption with a traditional backup approach, ever incremental backup approach and Phoenix. 
  • In addition to these, the storage page also shows the amount of data as seen on the source server(s) as of the last successful backup. Similar information is also shown at each individual server and server group level. 
  • A Server Storage report has been added to show this detailed information in a listed manner and this report can be generated either as an html page or in excel file format. 
  • Additionally, the dashboard has been updated to show an estimated storage used by the Site in a clean and easy view.

Action Required: None.

Backup Retry

 Phoenix now provides the ability to retry backup jobs within a scheduled backup window. This feature will ensure higher backup success if backup is failing due to transient issues in your environment. You can configure the retry setting (the number of retries and interval) as part of the Backup Policy.

Note: This feature is applicable only for scheduled backup and not for manually triggered backups (i.e. Backup Now).

Backup Proxy deployment Phoenix now provides re-designed usability experience while deploying and configuring VMware Backup Proxy in a single workflow through vSphere desktop/web client. This feature will work only if you have vCenter deployed in your environment. For standalone ESXi setup, you must perform the existing Command Line steps to configure Backup Proxy.
Unique Server Name Identifier Administrators can now assign a unique server name during pre-registration, post-registration, or post-configuration of a server to help identify a server in Server listing, Jobs, Reports, Alerts, etc. This is an optional setting to identify servers with complicated/cryptic FQDN/hostnames. This feature will also provide the capability to register servers with the same hostname in Phoenix.
Licensing-version 1

The following pricing and packaging changes have been addressed in this release:

  • Phoenix provides the following 3 types of  Licenses:
    • Business
    • Enterprise 
    • Elite

You can purchase the license based on your business need.

  • You can now avail the benefits of Phoenix de-duplication  technology as Phoenix is moving away from the traditional warm and cold storage. 

 

DRaaS Phoenix introduces the Disaster Recovery as a Service (DRaaS) functionality to extend its converged cloud-based data protection solution for enterprise infrastructure. Disaster Recovery as a Service (DRaaS)
RBAC to mainline

With the RBAC to Mainline enhancement, Phoenix now offers complete parity between Mainline Cloud and GovCloud, all GovCloud specific features have now been introduced to Mainline Cloud and vice-versa.

Here is the list of new features added to GovCloud and Public Cloud.

GovCloud Public cloud
File level Restore Site
Job Monitor Site Administrators

User Interface Enhancements

 

Note: To upgrade from version 3.5-r3954 to 4.0-r5132 do an RPM upgrade. To upgrade from versions earlier than 3.5-r3954 to 4.0-r5132 do a Backup proxy upgrade.

Cloud Cache
  • If you map/ re-map the server to the CloudCache, the first backup after the mapping will be a full backup to the CloudCache.
  • Added the following CloudCache alerts with different severity levels:
    • Cache storage space low.
    • Cache storage space full.
    • Cache not reachable for the server.
File Level Restore (FLR) enhancements Linux LVM is now supported. File Level Restore checklist

User Interface Enhancements

Phoenix provides a re-designed user interface to enable you to configure and manage Phoenix seamlessly.

Some of the UI enhancements are as follows:

  • Improved dashboard.
  • Information about the critical alerts displayed on the main menu bar.

 

File Level Restore (FLR)

With File Level Restore (FLR) you can restore files and folders within a restore point.  You can now retrieve one or more files from the backup image.

Note: If you want to upgrade from version 3.4 r3467 or below to version 3.5 r3954 or above, RPM upgrade is not supported. You must deploy a new backup proxy through OVA on the Downloads page.  

File Level Restore (FLR)
Web proxy configuration If you are using Web proxy in your environment, you can now configure it before activating Phoenix.
Job Monitor
  • To view the status of all initiated jobs.
  • Log upload and download.
  • Troubleshooting error message.
  • Added Jobs alerts
  • Enhancements for VMware on GovCloud
  • Added Storage and license errors.
  • To perform Full VM restore to the original location.
  • Restore to another registered vCenter or ESXi.
  • Support for vCenter 6.0 and ESXi 6.0.
  • Support for the backup of vRDM.
  • Added alerts for License and Storage.
Enhancements for VMware
  • To perform Full VM restore to original location.
  • Restore to another registered vCenter or ESXi.
  • Support for vCenter 6.0 and ESXi 6.0.
  • Support for the backup of vRDM.
Sites
  • Support for Sites.
  • Support for Site Administrator.
  • CloudCache enhancements.
Support for Server re-registration
  • Support for Server re-registration.
  • If you have migrated a registered server in Phoenix to a new server(replacement server), either as a part of your hardware refresh cycle or for disaster recovery purposes, you can use the Server re-registration option to replace the existing server with the replacement server in Phoenix.
Server Re-registration

Alerts

 

Added the following alerts with different severity levels:

  1. License

    • License Expired(Expiry date:month dd yyyy)

    • License About to Expire(Expiry date:month dd yyyy)

  1. Storage

    • Warm Storage Space Full

    • Cold Storage Space Full

    • Low Warm Storage Space Available (Usage: >80%)

    • Low Cold Storage Space Available (Usage: >80%)

Alerts
Enhancements for VMware
  • Support for SCSI HotAdd Transport mode.
  • Ability to restore Thin disk as Thin disk.
  • vmcontrol utility to enable CBT(Changed Block Tracking) on VMs.
Support for AWS govCloud

Phoenix is now supported in the AWS GovCloud, to allow US government agencies and customers to move sensitive workloads into the cloud by addressing their specific regulatory and compliance requirements. 

Note: Except for specific tasks described in the Support for GovCloud section, the administrator instructions for GovCloud remain the same. 

 
Support for VMware

Phoenix now supports VMware vCenter Server and VMware ESXi hypervisor respectively. To get started with backing up your VMware setup, you must deploy and configure Backup Proxy, which is available as a virtual appliance. Backup Proxy contains Phoenix agent and is bundled along with CentOS binaries. 

Backup Proxy backs up VMDK and VMX files across your virtual machines. You can choose to restore the VMDK files. 

VMware
Support for consumption-based pricing

You can now purchase the Phoenix license that includes tiers of warm storage and cold storage equivalent to the size of data that you backup. The new consumption-based pricing model allows you to purchase storage that is equivalent to the size of the data that you want to backup. This ensures significant cost savings, especially for long-term retention.

For exact licensing details, get in touch with your account executive or the Druva Support team.   
Support for retention policies Phoenix introduces retention policies that allow you to configure the length of time for which you want to retain your historic data. You can use retention policies to keep important data for future access, as well as purge data that is no longer required. Together with the "consumption-based pricing" model, Phoenix guarantees significant savings in storage for long term data retention and archival. Retention policies
Support for warm storage and cold storage You can now purchase warm storage and cold storage that best suits your data needs. Warm storage is used to hold server data that is no more than 90 days old while cold storage holds data that is transferred from warm storage, and is more than 90 days old. A combination of warm and cold storage ensures that both fresh data, as well as legacy data, are backed up. 

To determine the combination of warm and cold storage that best suits your needs, get in touch with your account executive or the Druva Support team.

To know more about storage, see Storage.   

Support for deleting servers and snapshots Phoenix supports delete operations for servers as well as snapshots. You can now delete data from servers that you are no longer using, such as when you deprecate server. You can also delete snapshots that you no longer require. Delete operations allow you to free storage, thus reclaiming storage space.  Servers
Support for SQL servers

Phoenix now supports Microsoft SQL Server version 2008 and 2012 respectively. With the support for full backups as well as differential backups, Phoenix effectively provides data protection and archival for database servers.

Configure SQL servers

Support for Phoenix CloudCache

Phoenix CloudCache is an on-premise caching server that ensures LAN-like experience while backing up your file servers and SQL servers. Phoenix agents use LAN to transfer data to Phoenix CloudCache configured within an organization's premises, thus ensuring speedy backups from servers to CloudCache. Phoenix CloudCache copies this data to Phoenix cloud at a later time such that the network and bandwidth are not compromised. 

Phoenix CloudCache
Enhanced administrator control

Phoenix supports two types of administrators -- the cloud administrators and the group administrators, for ensuring granular control. The enhanced administration experience means administrators can choose what they want to backup, initiate a restore anytime, monitor Phoenix activities, obtain regular reports, and manage their setups efficiently.

Account and administrator management

Deprecated features

Feature Brief description
Policy With the introduction of the Disaster Recovery (DR) Plan, the DR Policy has been deprecated.
Proxy Replacement

You can no longer replace a Backup Proxy.

In the earlier releases, you could replace backup proxy by navigating to VMware> ESXi/Hypervisor > Backup Proxies > Replace Backup Proxy.

Note: The support to this functionality was deprecated from the Proxy Load Balancing feature.

Detaching and attaching a backup policy

In the earlier releases, you could detach backup policies by navigating to Manage > Backup Policies > <Backup policy> or Manage > Server groups > <Server group>

After a detach operation, you could also attach backup policies by navigating to Manage > Backup Policies > <Backup policy> or Manage > Server groups > <Server group>.

Installer information

The filenames of the installers are listed in the following table. Use the filenames to ensure that you have the correct installer.

Note: To use the latest features, install the most-recent version of Phoenix agent. For more information, see Determine the Phoenix agent version

Product Bitness Revision    
Backup Proxy OVA file Druva_Phoenix_BackupProxy.ova
Phoenix agent  64-bit
  • Windows: Phoenix.msi
  • Linux: Phoenix.rpm
Phoenix agent 32-bit Windows: Phoenix_32
Phoenix CloudCache 64-bit (Windows Server 2012 compatibility only) PhoenixCacheServer

Revision information

Use this table to determine the features that your agent build revision supports.

Note: The table below lists all the agent built versions and the corresponding features released for that version. Refer to the table below to know the features available for Cloud or GovCloud.

Revision Support for previous features Newly-introduced features Public Cloud  GovCloud
  • Windows:  4.6.7-10428
  • Linux:  4.6.7-10212
  • Backup Proxy:  4.6.7-10212
  • Druva_Phoenix_BackupProxy.ova
Yes Automatically configure virtual machines for backup yes.png yes.png
  • Windows: 4.6.5-9240
  • Linux: 4.6.5-9240
  • Backup Proxy: 4.6.5-9240
  • Druva_Phoenix_BackupProxy.ova

Yes

  • File Backup and Restore in Deduplication-enabled Volume
  • Non-admin Email Subscription
  • Ubuntu File Server agent
  • Access Control Lists (ACL) support for Windows
yes.png yes.png
  • Windows: 4.6.4-9047
  • Linux4.6.4-9049
  • Backup Proxy4.6.4-9049
  • Druva_Phoenix_BackupProxy.ova
Yes
  • Single Sign-On 
  • Instrumentation
  • Job Enhancements
yes.png yes.png
  • Windows: 4.6.2-r8017
  • Linux4.6.3-8448
  • Backup Proxy4.6.3-8448
  • Druva_Phoenix_BackupProxy.ova
Yes

Disaster Recovery Failover Automation

yes.png yes.png
  • Windows: 4.6.2-r8017
  • Linux: 4.6.3r8368
  • Backup Proxy: 4.6.3r8368
  • Druva_Phoenix_BackupProxy.ova
Yes
  • Global DashboardStorage reporting changes

yes.png yes.png
  • Windows: 4.6.2-r8017
  • Linux: 4.6.2-r8017
  • Backup Proxy: 4.6.2-r8017
  • Druva_Phoenix_BackupProxy.ova
Yes Proxy Load Balancing yes.png yes.png
  • Windows: 4.6.2-r8017
  • Linux: 4.6.2-r8017
  • Backup Proxy: 4.6.2-r8017
  • Druva_Phoenix_BackupProxy.ova
Yes Job Improvements yes.png yes.png
  • Windows: 4.6.1-7430
  • Linux: 4.6.1-7433
  • Backup Proxy: 4.6.1-7433
  • Druva_Phoenix_BackupProxy.ova
Yes Backup for server with mixed workload (Backup Sets) yes.png yes.png
  • Windows: 4.6-r7165
  • Linux: 4.6-r7431
  • Backup Proxy: 4.6-r7431
  • Druva_Phoenix_BackupProxy.ova
Yes Job Based Logs yes.png yes.png
  • Windows: 4.5-r7091
  • Linux: 4.5-r7091
  • Backup Proxy: 4.5-r7091
  • Druva_Phoenix_BackupProxy.ova
Yes Agent upgrades through Phoenix portal yes.png yes.png
  • Windows: 4.4-r6780
  • Linux: 4.4-r6780
  • Backup Proxy: 4.4-r6780
  • Druva_Phoenix_BackupProxy.ova
Yes
  • VMware Performance Optimization
  • Changed Block Tracking
  • VMware Tools Quiescing
  • Backup Proxy replacement
yes.png yes.png
  • Windows: 4.3-r6381
  • Linux: 4.3-r6381
  • Backup Proxy: 4.3-r6381
  • Druva_Phoenix_BackupProxy.ova
Yes
  • CloudCache True Hot Restore
  • Performance Improvements
yes.png yes.png
  • Windows: 4.2-­r6121
  • Linux: 4.2-­r6183
  • Backup Proxy: 4.2-­r6183
  • Druva_Phoenix_BackupProxy.ova
Yes Storage Reporting yes.png yes.png
  • Windows: 4.2-­r6121
  • Linux: 4.2-­r6132
  • Backup Proxy: 4.2-­r6132
  • Druva_Phoenix_BackupProxy.ova
Yes Backup Retry yes.png yes.png
  • Windows: 4.2-­r6121
  • Linux: 4.2-­r6132
  • Backup Proxy:4.2-­r6132
  • Druva_Phoenix_BackupProxy.ova
Yes Backup Proxy deployment
 
yes.png yes.png
  • Windows: 4.2-­r6121
  • Linux:4.2-­r6132
  • Backup Proxy: 4.2-­r6132
  • Druva_Phoenix_BackupProxy.ova
Yes Unique Server Name Identifier yes.png yes.png
  • Windows: 4.1-r5350
  • Linux: 4.1-5339
  • Backup Proxy: 4.1-5339
  • Druva_Phoenix_BackupProxy.ova
Yes Licencing

yes.png

yes.png

  • Windows: 4.0-r5144
  • Linux4.0-r5132
  • Backup Proxy: 4.0-r5132
  • Druva_Phoenix_BackupProxy.ova
Yes DRaaS

yes.png

yes.png

  • Windows: 4.0-r5144
  • Linux:4.0-r5132
  • Backup Proxy:4.0-r5132
  • Druva_Phoenix_BackupProxy.ova
Yes RBAC to mainline

yes.png

yes.png

  • Windows3.5-r4311
  • Linux3.5-r4385
  • Backup Proxy: 3.5-r4385
  • Druva_Phoenix_BackupProxy.ova
Yes CloudCache

yes.png

yes.png
  • Backup Proxy3.5-r4269 Druva_Phoenix_BackupProxy.ova
Yes File Level Restore (FLR) enhancements

yes.png

yes.png
  • Windows: 3.5-r4041
  • Linux: 3.5-r4041
  • Backup Proxy: 3.5-r4041
    Druva_Phoenix_BackupProxy.ova
Yes User Interface Enhancements.  

yes.png

yes.png
  • Windows3.5-r3954
  • Linux:  3.5-r3954
  • Backup Proxy: 3.5-r3954
  • Druva_Phoenix_BackupProxy.ova
Yes File Level Restore (FLR)

yes.png

yes.png
  • Windows: 3.5-r3954
  • Linux:  3.5-r3954
  • Backup Proxy: 3.5-r3954
  • Druva_Phoenix_BackupProxy.ova
Yes Web proxy configuration

yes.png

yes.png
  • Windows:3.4r3471
  • Linux:  3.4-3467
  • Backup Proxy: 3.4r3467
    Druva_Phoenix_BackupProxy.ova
Yes Job Monitor

yes.png

yes.png
  • Windows:3.3r3472
  • Linux:  3.3-3470 
  • Backup Proxy: 3.3-3470
    Druva_Phoenix_BackupProxy.ova
Yes
  • VMware enhancements.
  • Storage and license alerts. 
yes.png

yes.png

  • Windows: 3.3 r2976
  • Linux:  3.3 r2976
  • Backup Proxy: 3.3 r2976
    Druva_Phoenix_BackupProxy.ova
Yes

To perform Full VM restore to original location.

yes.png

yes.png
  • Windows: 3.2 r2743
  • Linux:  3.2 r2824
  • Backup Proxy: 3.1 r2590
    Druva_Phoenix_BackupProxy.ova
Yes Support for Sites (Organizations). yes.png

yes.png

  • Windows: 3.1 r2590
  • Linux: 3.1 r2590
  • Backup Proxy: 3.1 r2590
Yes Support for Server re-registration.

yes.png

yes.png
  • Windows: 3.1 r2284
  • Linux: 3.1 r2284
  • Backup Proxy: 3.1 r2447
Yes

 Performance enhancements.

NoteUpgrade via RPM is supported only if the existing Backup Proxy version is 3.1x and above. Refer this article to determine your Backup Proxy version.

yes.png

yes.png
  • Windows: 3.1r2284
  • Linux: 3.1r2284
  • Backup Proxy: 3.1r2284
    Druva_Phoenix_BackupProxy.ova
Yes
  • Support for SCSI HotAdd Transport mode.
  • Ability to restore Thin disk as Thin disk.
  • vmcontrol utility to enable CBT(Changed Block Tracking) on VMs.
  • Added alerts for license and storage

yes.png

yes.png
  • Windows: 3.0-2044
  • Linux: 3.0-2044
  • Backup Proxy: 3.0-2044
  • Druva_Phoenix_BackupProxy.ova
Yes Support for AWS GovCloud

yes.png

yes.png

  • Windows: 3.0-1804
  • Linux: 3.0-1804
  • Backup Proxy: 3.0-1804
  • Druva_Phoenix_BackupProxy.ova
Yes Support for VMware

yes.png

NA

  • Windows: 2.0r1329
  • Linux: 2.0r1329
Yes
  • Support for retention policies
  • Support for warm storage and cold storage
  • Support for deleting servers and snapshots
NA NA
        Windows: 2.0r1097 Yes

Support for SQL servers version 2008 and 2012

NA NA
  • Windows: 1.3r816
  • Linux: 1.3r816
Yes Support for restore to a server other than the source server NA NA
  • Windows: r28339
  • Linux: r28339
Yes Support for Phoenix CloudCache NA NA

Fixed issues (From the Known issue topic)

The following table lists the issues fixed in subsequent releases. 

Issue Description  
ROBO-3383 An Internal Error  was displayed if you reconfigured a VM without taking a backup.  
ROBO-3387 Server and Server groups, were calculating bandwidth only based on backup jobs., displaying wrong bandwidth report.  
ROBO-3489  Unable to login into newly created Phoenix cloud instance.  
ROBO-3797 DR log request failed with an Internal error.  
ROBO-3473 If you change the IP address of a vhost , the entry with the old IP address still exists along with the new entry.   
ROBO-3954 /etc/host file is truncated if you renamed the Backup proxy host on Backup Proxy version below 4.6-r7431.  
ROBO-3959 The Site Dashboard displayed the "Ever Incremental Data" and "Last Backup Size" values as 0.  
ROBO-4067 Multiple daily storage stats entries are created for a single backup set.   
ROBO-4205
  • For the failed failover requests, the Failover History page displays the IP address values from the DR Plan in the Public IP and Private IP columns. 

  • If the failover request fails while assigning the private or public IP addresses to the instance, the instance is created in AWS. However, the respective instance ID is not displayed.

 
ROBO-4207 When an instance is launched for failover, the VM hostname is not carried over to the launched instance.  

 

 

  • Was this article helpful?