Skip to main content
Druva Documentation

Release notes

November 04, 2019

This cloud update has minor bug fixes.

Revision Information

The following table lists the versions of the agents released:

Platform Revision Public Cloud Gov Cloud
Windows 4.8.8-79929

 

 

tick.png

 

 

tick.png

Linux 4.8.8-79929    
VMware Backup Proxy 4.8.8-80128    
Hyper-V FLR Proxy Not applicable    
Phoenix Backup Store Not applicable

October 21, 2019

New Features

Create application-consistent, image-level virtual machine backups with advanced, agentless application-aware processing  

Starting today, if you enable application-aware processing for a virtual machine (VM), Phoenix has the ability to detect if a SQL Server is running inside a VM. And, it can use the Microsoft VSS framework and the virtual device interface to back up databases and its transaction logs. You can then restore the entire database, a point-in-time copy, or perform a marked transaction restore to VMs that have application-aware processing enabled. 

At the moment, Phoenix still has to restore a virtual machine and then restore databases to it. Yet, here's something that's in the works and coming soon: we're constantly working towards building the ability in Phoenix so that you can restore databases directly to the VM that hosts the SQL Server.

To learn more about how we are doing it, and what you need to do, see:

Customer action required: Upgrade the Phoenix Backup Proxies to the latest version.

Credentials store

To create application-aware backups, Phoenix needs to login to the virtual machines so that it can perform application-aware processing such as quiescing the application and performing log truncation. To do that, administrators should assign the virtual machine with an application service account for successful application-aware processing. So, we built a credential store that you can use to provide Phoenix the credentials of a virtual machine. You can now store credentials with Phoenix, and then assign them to VMs at scale. Otherwise, you'd have to manually enter credentials for each VM when you configure it for backup. All you need to do is assign a label to the credential that you store with Phoenix, and then use the label to identify it and assign it to multiple virtual machines when you configure application-aware backups for them. Based on the requirements, we can extend this to other workloads as well. 

For more information, see Credentials store.

Customer action required: No action required.

SQL APIs 

Druva now offers SQL APIs that you can use to organically interact with Phoenix for SQL workloads that Phoenix protects. You can integrate tools and applications with Phoenix by using the APIs to have a more customizable experience for reporting, analytics, and performing business functions for SQL servers that Druva Phoenix protects.

For more information, see API reference documentation on the Druva developer portal

Customer action required: No action required.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows Not applicable

 

 

tick.png

 

 

tick.png

Linux Not applicable    
VMware Backup Proxy 4.8.7-79132    
Hyper-V FLR Proxy Not applicable    
Phoenix Backup Store Not applicable    

October 7, 2019

Enhancement

Backup set identification was never so easy

We have made it easier for you to identify backup sets in each workload by assigning a unique name to it. This name acts as a unique identifier for the backup set. So, if you want to search for a backup set from a list of hundreds, just use the name as the search term. 

When you create a new backup set, a unique name is automatically assigned to it in the servername#bset<number> format. Moreover, you can rename the backup set at any given point in time.

Note: This feature is applicable only to the File Server, NAS, and MS-SQL workloads.

Will I have to update my existing backup sets manually?

Just sit back and relax. We will ensure that all your existing backup sets are labeled with a unique name. 

For more information on the user interface changes on the Phoenix console, refer to What is changing with the backup sets.

Customer action required: No action required.

Enhanced RTO for cold snapshots

With this release, we are excited to announce a significant enhancement in the restoration speed and improved RTO for your snapshots. All your cold snapshots will now move to the warm tier at no additional cost. What this means is that you will now experience faster and more efficient restoration of your data that initially had a higher RTO in the cold storage.

Customer action required: No action required.

Support for backup of databases on Oracle 18c and 19c

We have tested backup and restore of databases on Oracle 18c and 19c with Phoenix, and it works! Now, you can use Phoenix to backup and restore Oracle databases created and managed using Oracle Database 18c and 19c. For more information, see Support Matrix.

Customer action required: No action required.

Running the SQL Server backup using the command line

A few weeks ago when we added the ability to choose databases for backup, we had to take the ability to run a backup from the command line out. We did this because we were changing a couple of things under the hood. Now, that's back and you can run a backup again using the command line, with a slight modification. Because you can now name a backup set, you have to provide the name of the backup set in the command line instruction to run a backup for it. For your existing backup sets, we have already added a name, so that you can use it.

For more information on how to do this, see Trigger a backup using the command line

Customer action required: Upgrade the Windows Server Phoenix agent to the latest version.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.6-78269

 

 

tick.png

 

 

tick.png

Linux 4.8.6-78269    
VMware Backup Proxy 4.8.6-78114
Hyper-V FLR proxy Not applicable    
Phoenix Backup Store Not applicable

September 16, 2019

The following Phoenix update was released on September 16, 2019.

Enhancement

Enhanced Failback Recovery 

With this release, Druva takes a step forward in enhancing your disaster recovery process. We now bring to you a one-click, automated, failback disaster recovery solution to restore your failed over data. Struck by an unfortunate disaster and now want to restore your local setup? Go ahead and use our bullet-proof failback solution to move the workloads back to your data center in a single click and resume your IT operations. The failback mechanism seamlessly restores your failed over EC2 instances from your AWS account back to your virtualization data center.

To know more about how it works, check out the following articles:

Customer action required: Ready to use our latest DR failback offering? Here’s how you can quickly perform these tiny bits to get started:

  • For the existing customers: Upgrade the Phoenix backup proxy to version 4.8.6. Have multiple proxies deployed in your setup? No worries! Upgrade at least one Phoenix AWS proxy and backup proxy to version 4.8.6.

  • For new customers: Simply deploy a new Phoenix AWS proxy of version 4.8.6.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.6-76073

 

 

tick.png

 

 

tick.png

Linux 4.8.6-76073    
VMware Backup Proxy 4.8.6-76224
Hyper-V FLR proxy Not applicable    
Phoenix Backup Store Not applicable

August 26, 2019

The following Phoenix update was released on August 26, 2019.

New Features

Ability to choose databases on a SQL Server instance for backup 

With this release, you will get an option to choose databases on an instance that you want to back up with Phoenix. 

Now: When you configure a SQL Server backup, you can create multiple backup sets per instance in which you can choose which databases you want Phoenix to back up and which databases to exclude from a backup. You can also add new backup sets to the registered instance with different databases selected for backup.
 
Earlier: When you configured a SQL Server backup, one backup set was created per instance. The backup set would include all the databases in it. For example, if there are two SQL Server instances on the Windows Server host, Phoenix would create two backup sets, one each for an instance. Backup set one for the first instance included the databases on the first instance and backup set two for the second instance included the databases on the second instance for the backup. You only got an option to exclude databases from backup.

For more information, see:

Customer action required: Upgrade the Phoenix agent to the latest version. The Phoenix agents released on or after August 26th, 2019 can discover databases on the SQL Server. After you upgrade the agent and the agent discovers the databases on the SQL Server, you can update the older backup set or add new backup sets to choose the databases that you want to back up. 

Note: After upgrading your agent, if you add a database to the SQL Server, Phoenix does not automatically add it to a backup set unless you use an inclusion filter in a backup set or manually add it to a backup set. In addition, the command line backup method for SQL Server will not be available after you upgrade the agent. 

Alerts APIs

Druva now offers Alerts APIs that you can use to organically interact with Phoenix to fetch backup failure alerts. You can integrate tools and applications with Phoenix by using these APIs to have a more customizable experience for reporting and analytics. 

For more information, see API reference documentation on the Druva developer portal

Customer action required: No action required.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.5-73715

 

 

tick.png

 

 

tick.png

Linux 4.8.5-73715    
VMware Backup Proxy 4.8.5-73715
Hyper-V FLR proxy N/A    
Phoenix Backup Store N/A    

August 5, 2019

The following Phoenix updates are released on August 5, 2019.

Enhancements

Enhanced Recovery workflow with improved RTO

With this release, Druva Phoenix provides enhancements to the failover workflow. During failover, Phoenix DRaaS converts all virtual machines configured in a DR plan in parallel thereby ensuring that virtual machines across multiple steps have the same RTOs. This will ensure that customers are able to meet their RTO requirements irrespective of the number of steps involved within the DR plan.

For more information, see About recovery workflow.

Customer action required: No action required.

Use EBS snapshots to restore EC2 instances, EBS volumes, and files

On July 1, 2019, we announced that Phoenix can protect your EC2 instances by creating AMIs and using these AMIs to restore the instances. With this release, in addition to creating AMIs, you can now back up the data on your Amazon EBS volumes to Amazon S3 by taking point-in-time snapshots and then restore these snapshots as EC2 instances, specific files, and EBS volumes.

Phoenix provides the agile flexibility to improve the speed and reliability of your backups and restores, and with this added capability, we enhance this in the following ways:

  • Rapid backup and restore: With snapshots, your data is quickly backed up to Amazon S3 and the restore process is rapid. 

  • Granular file-level restore: You now have the ability to recover a single file rather than an entire volume or instance, which is important especially if you simply want to restore selective files. 

  • Snapshot restore as a volume: You can restore a snapshot as a volume and then later attach it to your EC2 instance. 

To know more about this enhancement, see Backup and Restore AWS resources.

Customer action required: No action required

Hyper-V reporting APIs

Druva now offers APIs that you can use to organically interact with Phoenix for Hyper-V workloads that Phoenix protects. Integrate tools and applications with Phoenix using the APIs to have a more customizable experience for reporting, analytics, and performing business functions for Hyper-V hosts and virtual machines that Druva Phoenix protects.

For more information, see API reference documentation on the Druva developer portal

Customer action required: No action required

Fixed Issues

The following issue has been fixed in this release.

  • The toTime parameter of the File server, NAS share, and VMware Reporting APIs defaulted its value (time) to midnight of the day (00:00 hrs) irrespective of the specified time. 

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.4-72004

 

 

tick.png

 

 

tick.png

Linux 4.8.4-72004
VMware Backup Proxy Not applicable
Hyper-V FLR Proxy Not applicable
Phoenix Backup Store Not applicable

July 15, 2019

The following Phoenix updates are released on July 15, 2019.

New Feature

Druva Phoenix APIs available on the API documentation portal

We have rolled out an API documentation portal for developers with Druva Phoenix APIs that help you create reports to explore, get insights, or answer important questions about your jobs and data. This API-driven portal provides a developer-friendly view of all the endpoints offered by Druva and features the following:

  • An easy, comprehensive way to identify all the requests and responses along with their data type.

  • Effective developer interaction with the response objects directly on the portal by expanding and collapsing the response objects.

  • Schemas for each response are provided along with each endpoint to mock the APIs before actual testing.

  • Comprehensive API errors and their explanations for each endpoint.

  • Ease of distinguishing the command and code snippets and helping developers to copy them easily.

  • Capability to easily search through the endpoints and the description.

With this release, we provide you with the following Phoenix APIs: 

  • AuditTrail 

  • CloudCache

  • File Server

  • NAS 

  • Organization 

  • Storage 

  • VMWare

Experience our API documentation portal for developers at https://developer.druva.com.

Customer action required: If you are using Phoenix and inSync, ensure that your Phoenix and inSync accounts are merged before you use the APIs. For more information, contact Druva Support.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.3-69215

      

tick.png

 

tick.png

Linux 4.8.3-69215
VMware Backup Proxy 4.8.3-69446
Hyper-V FLR Proxy Not applicable
Phoenix Backup Store Not applicable

July 1, 2019

The following Phoenix updates are released on July 1, 2019.

New Feature

New resources added to the protection sphere of Phoenix: Amazon EC2 instances

As Druva Phoenix continues its flight higher than ever, hitting the right balance of needs has led it to be used in production by various organizations across the globe who are looking to protect their data in the form of multiple workloads. With our long history in protecting workloads such as files, Oracle databases, NAS shares, Hyper-V virtual machines, MS-SQL databases, and VMware virtual machines, Phoenix can now protect your EC2 instances too. 

You now have a single pane of glass view for multiple workloads (including cloud-native workloads) irrespective of their deployment models. Say goodbye to the concerns of buying separate products to protect data on-premise and in the cloud.

For more information, see Backup and Restore AWS resources.

Customer action required: No action required.

Fixed Issues

Unable to use the DRProxy HOTFIX_AMIS parameter.
Partial AMI failover job triggered on the older Phoenix AWS proxy stays in running state.
Virtual disks that have the character '/' in the name are not getting excluded.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows N/A

 

tick.png

 

tick.png

Linux N/A
VMware Backup Proxy 4.8.3-68312
Hyper-V FLR Proxy N/A
Phoenix Backup Store N/A

June 17, 2019

The following Phoenix updates are released on June 17, 2019:

New Features

Exporting data out of Phoenix Cloud for Compliance and Disaster Recovery test

Druva Phoenix provides an optimal way to obtain your organization’s large data stored in the Phoenix Cloud.​​​ The requested data is shipped to your data center using an AWS Snowball Edge. This service enables you to export data in the following situations:

  • To recover data when a disaster strikes your organization
  • To ensure that the data stored in the Phoenix Cloud comply with your organization's data
  • To obtain complete data of your organization on the termination of your contract with Druva

Phoenix provides this feature as an add-on service and this service is charged separately. It is not a part of the standard Phoenix subscription. Contact the Druva Sales team for more details.

For more information, see Bulk data export using AWS Snowball Edge.

Customer action required: No action required.

Improved clean up of Phoenix agent on uninstall from Linux

Druva Phoenix now provides a prompt that lets you clean up configuration files if you choose to uninstall them using the command line on a Linux server.  In addition, if you plan to upgrade the Phoenix agent, you can choose to retain the configuration files. 

Druva Phoenix also provides environment variables in the Phoenix agent that let you choose whether you want to clean up configuration files or retain them at the time of uninstalling the Phoenix agent. 

If you plan to upgrade the Phoenix agent, ensure that you do not remove the configuration files. 

For more information, see:

Customer action required: Upgrade the Phoenix agent to the latest version.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.3-67213

 

tick.png

 

tick.png

Linux 4.8.3-67213
VMware Backup Proxy 4.8.3-67103
Hyper-V FLR Proxy 4.8.3-67103
Phoenix Backup Store 4.8.3-67213

June 03, 2019

The following Phoenix updates are released on June 03, 2019:

New Features

Modification of the retention policy behavior

With the aim to achieve easier snapshot management and increased storage efficiency, Druva Phoenix introduces modifications in the retention policy behavior, which are as follows:

  • The retention period is now restricted to a minimum number of 14 days. It applies to all the new retention policies that you create.

  • Any changes that you make to the existing retention policies are now applied to all the new as well as the existing snapshots.

Customer action required: No action required.

Automating deployment of virtual machine infrastructure in Phoenix

Druva Phoenix introduces the next level of automation for your VMware infrastructure deployment, which now includes auto configuration based on:

  • Datastores
  • Hosts and Clusters
  • Tags, assigned to any object in your VMware infrastructure

Use these capabilities to automate the configuration of your virtual machines to specific backup policies and hence, save time and increase efficiency and productivity.

Customer action required: Upgrade the Phoenix agent to the latest version. Tag support requires VMware vCenter 6.5.0 or later.

For more information, see the following documentation:

Enhancements to the Phoenix CloudCache

With this release, Druva extends the existing capabilities of the Phoenix CloudCache. The key enhancements include the following:

  • Added a new graph, Data Sync Trend,  which allows you to view the statistics of the synced and unsynced data (not uploaded from the Phoenix CloudCache to the Phoenix Cloud) in the last 30 days.

  • Added new alerts to notify administrators for the following Phoenix CloudCache issues:

    • A Phoenix CloudCache volume is not mounted.

    • A Phoenix CloudCache is not able to read or write data to the CloudCache during the backup, restore, or the synchronization schedule.

    • The data upload rate from the Phoenix CloudCache to the Phoenix Cloud is significantly low.

    • The Phoenix Cloud is not able to connect to the Phoenix CloudCache during the synchronization schedule.

Customer action required: No action required.

For more information, see the following documentation:

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.3-65392

 

tick.png

 

tick.png

Linux 4.8.3-65392
VMware Backup Proxy 4.8.3-65732
Hyper-V FLR Proxy Not Applicable
Phoenix Backup Store Not Applicable

May 20, 2019

The following Phoenix updates are released on May 20, 2019:

New Features

Enhancements to the Disaster Recovery solution

With this release, Druva Phoenix introduces an enhanced disaster recovery solution to improve business continuity to provide greater control of the failover process, automated one-click deployment of virtual machines for failover, tighter AWS integration, and simplified orchestration and testing. As applications become more complex, the interdependencies between virtual machines become more sophisticated. For an application-consistent recovery, organizations are looking for automated solutions to bring up their virtual machines with minimal intervention and dependencies.

With the introduction of automated runbook execution and one-click failover, IT can now automate the manual tasks for deploying proxy and creating the required IAM roles and policies using the AWS CloudFormation template. With failover automation, the key tasks performed during failover are automated by providing additional target instance properties, network pre-configurations, virtual machine boot-ordering, and scripting for custom recovery workflows.

Customer action required: To use the latest DR orchestration features, perform the following actions:

  • For new customers: Deploy a new Phoenix AWS proxy version 4.8.2.

  • For the existing customers: Upgrade the Phoenix backup proxy to version 4.8.2. If you have deployed multiple proxies, you must upgrade at least one Phoenix AWS proxy and backup proxy to version 4.8.2 and then update the IAM policy of the IAM role attached to it. To update an IAM policy, see How can I update my IAM policy.

For more information, see the following documentation:

MS-SQL Server as an independent workload

With this release, Druva Phoenix starts considering an MS-SQL Server workload independent of a Windows Server so that administrators can leverage role-based access control (RBAC) independently for MS-SQL Servers. Now, to back up an MS-SQL Server database, you can register an MS-SQL Server host from the MS-SQL Server page itself and add MS-SQL Server backup sets to the host. With this feature, separate administrative groups can be created to manage MS-SQL Server database backups and file and folder backups on Windows hosts.  

Note: When you add a SQL Server host, it is also registered with Phoenix as a Windows Server and you can access it using the Protect > Windows/Linux Servers option on the top menu if you want to add file backup sets to it. However, to manage SQL Server backup sets on a Windows Server, you have to navigate to the server from the Protect > MS-SQL Servers page of its organization. Similarly, to manage file backup sets, navigate to the server from the Protect > Windows/Linux servers page of the organization. 

Customer action required: No action required.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.2-64432

 

tick.png

 

tick.png

Linux 4.8.2-64432
VMware Backup Proxy 4.8.2-64432
Hyper-V FLR Proxy Not applicable
Phoenix Backup Store Not applicable

May 6, 2019

The following Phoenix updates are released on May 6, 2019:

New Features

File search for quick restore

Phoenix now makes it easier for you to search files across snapshots within a backup set that you want to restore. Phoenix introduces a search bar along with advanced filter options on the Restore Data dialog box. This enables you to search for a particular file to restore without having to browse through all of the backed up files or snapshots.

You can perform a full-text search or search for files of a certain type, such as MS Office files, HTML files, audio files, PDF files, and executable files, and restore them.

Note: In the current release, the search feature is limited only to the files and folders backed up from Windows/Linux servers and NAS shares.

For more information on using the search feature and search filters, see the Search for files section.

SearchforrestoreGIF_new.gif

Action required: No action required.

Support for backup of files and folders on ReFS

Phoenix can now back up files and folders on the Resilient File System (ReFS) volumes. Phoenix also allows you to back up and restore data from and to the NTFS and ReFS volumes.

To know more about the  ReFS versions that Phoenix supports, see System requirements.

Customer action required: Upgrade the Phoenix agent to the latest revision.

File scan enhancement Windows servers

With this enhancement, Druva Phoenix significantly improves the file scan performance during incremental backups.

After you upgrade the Phoenix agent, you can expect the first backup to be slightly slower because of the metadata processing. And, thereafter all the incremental scans will be much quicker.

Customer action required: Upgrade the Phoenix agent to the latest revision.

Support for new operating systems for files, folders, and NAS shares

 Phoenix now supports the backup and restore of files and folders, and NAS shares on the following operating systems.

  • Windows Server 2019 (64-bit)
  • CentOS 6.9, 6.10,  7.4, 7.5, and 7.6 (64-bit)
  • Red Hat Enterprise Linux (RHEL) 6.10, 7.5, and 7.6 (64-bit)
  • Oracle Linux 6.9, 6.10, 7.5, and 7.6 (64-bit)
  • SUSE Linux Enterprise Server (SLES) 12.4 LTS (64-bit)
  • Ubuntu 18.04 LTS (64-bit)

For more information, see Support matrix.

Customer action required: Upgrade the Phoenix agent to the latest revision.

Deprecated term

With this release, Phoenix will no longer use the Overage term to denote the excess amount of credits utilized after consumption of all your purchased credits. The Credit Balance field on the dashboard will now display the excess credits consumed in red preceded by a minus sign as shown in the following screenshot:

all_org_dash_rn.png

For more information, see:

Action required: No action required.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.1-63534

 

tick.png

 

tick.png

Linux 4.8.1-63534
VMware Backup Proxy 4.8.1-62836
Hyper-V FLR Proxy Not applicable
Phoenix Backup Store 4.8.1-62836

April 15, 2019

The following Phoenix update is released on April 15, 2019:

New Features

File scan enhancement for NAS shares and Linux File servers

With this enhancement, Druva Phoenix significantly improves the file scan performance during incremental backups.

Additionally, Phoenix now comes with a standalone Scanner CLI utility bundled with the Phoenix agent.  This utility runs independently and provides you with all the telemetry information to get insight into the file system and NAS share. For more information, refer to Scanner CLI utility.

After you upgrade the Phoenix agent, you can expect the first backup to be slightly slower because of the metadata processing. And, thereafter all the incremental scans will be much quicker.

Note: Currently, this enhancement is applicable to the NAS  Shares (NFS and SMB) and Linux File servers.

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

Support for encrypted MS-SQL databases

Phoenix can back up and restore databases encrypted using Transparent Data Encryption (TDE). However, ensure that the certificate and key used to encrypt the backed up database must be present on the SQL server to which you restore the database. 

Note: Phoenix does not back up encryption keys and certificates.

Action required: No action required.

Support for RHEL 6.9 and 7.4

Phoenix certifies backup and restore of files and folders on Red Hat Enterprise Linux (RHEL) (64-bit) 6.9 and 7.4.

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

April 1, 2019

The following Phoenix update is released on April 1, 2019:

New Feature

Enhancements to Phoenix backup proxy for VMware

  • Support for web proxy using Kerberos authentication method for VMware backups
    With the latest Phoenix backup proxy for VMware, you can choose Kerberos as the authentication method to connect to a web proxy when you specify the network settings. For more information, see: 
  • Handling of pagefile.sys and hiberfil.sys files while backing up Windows VMware virtual machines
    With the latest version, Phoenix backup proxy excludes the content of these files from backup. For more information, see VMware Backup and Restore FAQs.

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

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.0-58452

 

tick.png

 

tick.png

Linux 4.8.0-58452
VMware Backup Proxy 4.8.0-58452
Hyper-V FLR Proxy 4.8.0-53656
Phoenix Backup Store 4.8.0-59292

February 18, 2019

The following Phoenix update is released for the cloud update on February 18, 2019:

New Feature

Backup optimization by using Snowball Edge as a seeding device

Druva Phoenix utilizes the advanced capabilities of AWS Snowball Edge to facilitate a fast transition of data to the Phoenix Cloud in a bandwidth-compromised environment. After the data is transferred to the Phoenix Cloud, Phoenix makes the restore points available for the mapped backup sets.

With AWS Snowball Edge, Phoenix allows enterprises to freely move data between the on-premise storage and the Phoenix Cloud without the complexity and cost of legacy hardware; thus, enabling them to speed up their backup.

Additional benefits that you can expect from this integration include:

  • Plug and play workload mobility: With AWS Snowball Edge, you can apply backup policies and backup or restore directly to and from the device. With global deduplication technology, only a single copy of data is stored; thus, ensuring maximum storage on the device.
  • Ship petabytes securely: AWS Snowball Edge devices use tamper-evident enclosures, 256-bit encryption, and industry-standard Trusted Platform Modules (TPM) designed to ensure both security and full chain-of-custody for your data.

Phoenix provides this feature as an add-on service and this service may be charged separately. Contact the Druva Sales team for more details.

Action required: No action required.

For more information, see the Backup Optimization by using Snowball Edge as seeding device guide and the Activating Snowball Edge for Phoenix data seeding video.​​​​​​ ​

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.0-55243

 

tick.png

 

tick.png

Linux 4.8.0-55243
VMware Backup Proxy NA
Hyper-V FLR Proxy NA
Phoenix Backup Store 4.8.0-55398

February 4, 2019

The following Phoenix update is released for the cloud update on February 4, 2019:

New Feature

  • Support for Oracle Databases

Support for Oracle Databases

With this release, Phoenix is now an Oracle recognized database backup solution provider. For more information, see Oracle Backup Solutions Program (BSP). Phoenix provides a robust solution that works with Oracle Recovery Manager (RMAN) to:

  • Protect the Oracle RMAN backups on an NFS target on the Phoenix Backup Store
  • Manage the Oracle Database backup lifecycle

For more information, see Backup and Restore Oracle Databases

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.0-53656

 

tick.png

 

tick.png

Linux 4.8.0-53656
VMware backup proxy 4.8.0-53656
Hyper-V FLR proxy 4.8.0-53656
Phoenix Backup Store 4.8.0-53656

January 21, 2019

The following Phoenix update is released for the cloud update on January 21, 2019:

New Features

Enhanced disaster recovery solution

With this release, Druva Phoenix introduces an enhanced disaster recovery solution to convert the VMware virtual machine backup images to the AWS EC2 instances. This solution replaces the usage of VM Import for conversion. It drastically reduces the time required for the conversion process and provides predictable and improved RPO to our customers resulting in the faster virtual machine data restores.

In addition, administrators can now monitor the state of the failover process on the Phoenix Management Console.

Action required: For customers using a Phoenix AWS proxy version earlier than 4.8.0, install a new Phoenix AWS proxy version 4.8.0 or later. For more information, see Launch Phoenix AWS Proxy and Register Phoenix AWS Proxy.

For more information, see:

Support for VMware vSphere virtual volumes (VVols)

Phoenix now supports the following:

  • Backup of the virtual machine that resides on virtual volumes with related storage based management policy applied to it
  • Restore of the virtual machine that is backed up from any datastore type VMFS, vSAN to VVols
  • Restore of the virtual machine backed up from VVol datastore to another type of datastores, such as VMFS, vSAN
  • Restore of the virtual machine with storage-based management policy applied to it to the original location

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

Support for backup of VMware virtual machines on NFSv4.1 and NFSv4.2

Phoenix can now back up VMware virtual machines from the vCenter/ESXi hosts with a datastore that uses NFSv4.1 and NFSv4.2.

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

Phoenix Management Console UI enhancements

With the aim to constantly enhance the user experience, Druva is excited to introduce a refreshed Phoenix Management Console menu bar. A few options on the menu bar are reorganized and a few icons are removed. However, there is no change in the functionality in the product.

The key enhancements include the following:

  • A new Global navigation panel has been added to quickly switch between products and configure administrator settings.
  • The Settings menu is now represented by the Settings_icon.png icon.
  • The Administrator submenu is renamed to Manage Administrators and is now available under Settings_icon.png.
  • The Download Agent option is now a submenu under Settings_icon.png.
  • The Documentation menu is now a submenu under Help_icon.png.
  • The Alerts menu is now represented by the Alerts.png icon.
  • The password policy and single sign-on settings are available under Settings_icon.png > Phoenix Settings.

Action required: No action required.

Fixed Issues

Issue Description

ROBO-11193

A transaction log backup starts running when a full/differential backup job is already in progress for an MS-SQL server.

Revision Information

Platform Revision Public Cloud Gov Cloud
Windows 4.8.0-53656

 

tick.png

 

tick.png

Linux 4.8.0-53656
VMware backup proxy 4.8.0-53656
Hyper-V FLR proxy 4.8.0-53656

January 7, 2019

The following Phoenix update is released for the cloud update on January 7, 2019:

New Feature

Analytics

The Analytics feature gives you an insight into your deployment of various resources with Druva Phoenix especially with respect to credits and storage consumption. Through various forms of graphs and widgets, you can get an in-depth analysis of the total credits and storage, source + changes data, current source data, the projected timeline for exhaustion of the credit balance, source reduction factor, and the change rates. It also enables you to view the events and the audit trails for the same.  This feature is enabled by default for all accounts.

As a Cloud administrator, you can use this feature to:

  • View the Phoenix credits consumption in the last 90 days 

    Note: To begin with, the existing users can view the analytics data for the last 30 days. They can view the analytics data for 90 days after February 17, 2019. For new accounts, the analytics data for 90 days is visible upon their completion of the same period.
  • Select a backup set and view its details, such as current source, source + changes, and daily changes for the last 30 days

  • Compare the data size in the existing source with the new backup sets in the given time period

  • View the current source reduction factor

  • Get a visual overview of the credit balance, total source + changes, total current source data, and total storage consumed over a given time period in the form of graphs

  • View the captured events, the number of events for a specific date, and the event details

To access the analytics data, on the menu bar, select All Organizations and click Analytics.

CA42.png

For more information, see Analytics.

Action required: No action required.

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.  

restore-enhancements.png

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

 

tick.png

 

tick.png

Linux Not Applicable
VMware backup proxy Not Applicable
Hyper-V FLR proxy Not Applicable