📝 Note

​ These are archived release announcements, and some links might be inactive.

Druva now lets organizations configure Phoenix Backup Store with Oracle Enterprise Manager (OEM) to simplify database backup management on the Oracle RMAN Database hosts in their data centers and in the AWS Cloud. You can now schedule and manage backups on the Oracle RMAN Database hosts in the data center and in the AWS Cloud using the OEM. It also simplifies the script management process during backups and lets you run customized scripts during the backups. For more information, see Configure Oracle Enterprise Manager with Phoenix Backup Store and Template scripts for configuring OEM.

With the release, the following operating systems are supported:

For more information, see DRaaS support matrix.

Customer action required: Upgrade the Phoenix AWS Proxy to version 4.9.2-104913 and the VMware backup proxy to version 4.9.2-104913. You can download the Phoenix AWS Proxy from the Downloads page.

With the release, the following instance types are supported for failover:

For more information, see DRaaS support matrix.

Customer action required: None

With the implementation of AWS PrivateLink (If you have deployed a Phoenix AWS proxy version 4.9.1-101573 or later), when you create a new DR Plan, add VMs to a DR plan, or when you update failover settings, only the existing IAM roles will be displayed in the IAM Role drop-down. If you have created a new IAM role in your AWS account, you need to manually type the name of the IAM role which is the IAM instance profile ARL name.

Create a DR plan

For more information, see ​​​​​​ Create a DR plan.

Add VMs

For more information, see Manage Virtual Machines.

Failover settings

For more information, see Manage disaster recovery failover.

Customer action required: None

The VMware backup policy creation user interface is enhanced for easier operations. Also, you can now schedule backups at hourly intervals.

For more information see, Manage backup policy.

New access point

Backup policy creation wizard

Backup policy management

For VMware workloads, for restoring MS SQL application-aware restore and now you can:

For more information, see Restore prerequisites and considerations.

Customer action required: Upgrade the VMware backup proxy to version 4.9.2-104913. You can download the Phoenix AWS Proxy from the Downloads page.

Phoenix will not make any default file type exclusions, or inclusions in the file server and NAS content rules created post 21 December 2020. You can now choose to exclude or include predefined file types, custom extensions, and file name patterns. Phoenix also allows you to make the entered folder paths, extensions, and file name patterns on Linux servers and NFS shares case insensitive.

For more information see Manage content rules in file servers and Manage Content Rules in NAS.

Customer action required: Upgrade the Phoenix agent to version 4.9.1-103398 to use the Ignore case sensitive file/folder name path for Linux servers and NFS shares feature.

We have enhanced the file server and NAS APIs wherein, the BackupContentStruct structure returns the content rule information, such as the list of folders, file types, extensions, and patterns included or excluded from the backup. For more information, see BackupContentStruct and NASBackupContentStruct on the API reference documentation on the Druva developer portal.

Customer action required: No action required.

Phoenix now supports Amazon FSx for Windows shares and Amazon EFS shares for backups and restores. You can protect Amazon FSx for Windows shares using a Windows proxy, and protect Amazon EFS shares using a Linux proxy. For more information, see Phoenix support for Amazon FSx for Windows and Amazon EFS

Customer action required: No action required.

The newly redesigned MS-SQL Servers page in Phoenix has an intuitive user interface that lets you accomplish critical tasks with ease. Some of the key highlights of the new user interface are:

All SQL Resources details page

The redesigned All SQL Resource details page lets you see all the configured backup sets for the instance or availability group at a glance. You can view more details about the configured backup sets, create new backup sets, backup or restore data from this page itself.

Create Backup Set page

The new Create Backup Set page allows you to configure everything required for SQL backup sets from one single place.

Register New Server page

The newly designed Register New Server page lets you check prerequisites for the SQL agent, download the agent and activate the agent all from a single place.

Backup Policies page

The new SQL Backup Policies page lets you create new policies and duplicate existing ones. This page lists all the existing SQL backup policies.

SQL jobs page

The newly added SQL jobs page lists all the SQL backup, restore and log request jobs. You can see the status of running jobs and details of the completed jobs. You can also filter the SQL jobs by job type, status, and started in.

A new SQL Restore data page

The new restore data page lets you select from a snapshot restore, point in time restore, and a transaction mark restore. Depending upon the chosen restore type, select the other settings and databases and perform a restore.

For more information, see

For VMware, to perform application-aware restores of MS SQL databases, now you need to simply upgrade one of the backup proxies and proceed with the restore. With this enhancement, you no longer need to deploy a fresh backup proxy which was a requirement earlier.

Customer action required: Upgrade the backup proxy to version 4.9.2. For more information, see Upgrade backup proxy.

Here are some of the upcoming enhancements with the December 21, 2020 release.

The VMware backup policy creation user interface is enhanced for easier operations. Also, you can now schedule backups at hourly intervals.

New access point

Backup policy creation wizard

Backup policy management

The redesigned MS-SQL Servers page in Phoenix is intuitive and helps you perform critical tasks with ease. You will experience simplified workflows for registering SQL servers, creating backup sets, restoring SQL databases, and much more.

Customer action required: No action required.

The communication between AWS services and Druva services used for DRaaS, is now done through AWS PrivateLink instead of the internet gateway.

AWS PrivateLink provides private connectivity between VPCs and services hosted on AWS or on-premises, securely on the Amazon network. By providing a private endpoint to access the services, AWS PrivateLink ensures the traffic is not exposed to the public internet. It also makes it easy to connect services across different accounts and VPCs to further simplify network architecture.

Customer action required: Install Phoenix AWS Proxy version 4.9.1-101573.
​
When you deploy the Phoenix AWS Proxy, Druva deploys VPC endpoints for required services and deploys a Route 53 hosted zone for the VPC.

❗ Important

This capability is available only with a fresh deployment and not with an upgrade of the Phoenix AWS proxy.

For existing customers, deploy a new Phoenix AWS proxy using the new cloud formation template and delete the existing Phoenix AWS proxy.

For more information, see Deploy Phoenix AWS proxy.

We have enhanced the Smart Scan user interface so that it is easier for you to decide whether to enable Smart Scan in your backup policy or not. Smart Scan lets you skip files on your Linux file servers and NAS shares that have not changed recently. Skipping these files from backup scans makes incremental backups faster.

Customer action needed: None.

We have changed our compression algorithm from ZLIB to ZSTD. New Phoenix users (23 November 2020 and later) with File Server and NAS workloads can now experience optimized resource utilization in addition to better compression, reduced storage, and faster backups and restores. Existing users with File Server and NAS workloads can experience these benefits starting in January 2021 but need to ensure that:

Customer action needed:Existing customers with File server and NAS workloads must upgrade all the Phoenix agents to version 4.9.0 or later and CloudCache agents to version 3.9 or later.

This release brings an enhanced credit limits feature for you to have granular control over defining and managing your organization’s credit limits. Credit limits enable you to configure the number of credits that an organization can consume. The updated Credit Limits brings the following new capabilities:

For more information on managing credit limits, refer to Credit Limits.

You can now browse to mount points while restoring SQL databases to alternate locations.

For more information, see Restore SQL server databases using snapshots.

We have redesigned the Analytics page that has an intuitive user interface for easier operations.

For more information, see View Analytics page.

Customer action required: None

Phoenix DRaaS now supports the following:

For more information, see DRaaS support matrix.

Customer action required: None

Druva will end the support for TLS 1.0 for Phoenix Clients on November 23, 2020. As you may be aware, TLS 1.0 is now obsolete and is known to have several security vulnerabilities. IETF, as well as several government agencies and global compliance regulations have mandated that TLS 1.0 must not be used.

Phoenix Clients lower than version 4.7.6-47047 use TLS 1.0 and will no longer be able to connect to the Phoenix Cloud. For uninterrupted services, it is mandatory to upgrade to the latest Phoenix Client version supported by Druva. Similarly, Phoenix CloudCache lower than version 3.7-47047 use TLS 1.0 to communicate to the cloud. Please upgrade the Phoenix CloudCache server to the latest version.

Customer action needed: You must upgrade all the configured Phoenix Clients and Phoenix CloudCache to the latest version.

If the Phoenix Client is installed on Windows Server 2003 (EOL), you need to migrate to the supported platform as per the Phoenix Support matrix.

You can now restore MS SQL server databases from application-aware backups without requiring to restore the entire virtual machine. You can restore the database to its original location or an alternate location. You can also restore just the database files from a snapshot.
​
Also, when you perform a full VM restore of MS SQL virtual machines (application-aware), the restored databases will be application-consistent.

Watch this video for a quick process overview;

Note:This enhancement is only applicable to VMware on-premises as the NFS datastore is not supported by VMware cloud.

For more information, see Restore Microsoft SQL Server databases on VMware virtual machines.

Customer action required: Deploy a fresh additional backup proxy and provision a Windows staging virtual machine.

You can now create content rules in NAS. You can either use existing content rules or specify custom content and save it as a new rule.

For more information, see Manage Content Rules in NAS

Customer action required: None

This release brings an enhanced version of the Phoenix Backup Store for Oracle Server. The design changes and improvements to the Phoenix Backup Store now provide you with an in-depth experience in reporting and monitoring Oracle backups.

Customer action needed:

When you configure your virtual machines for backup, you can select local storage to store backups locally by mapping a Phoenix CloudCache.

The option is available when you create or edit an auto-configuration rule or manually configure or reconfigure virtual machines for backup.

For more information, see Getting started with configuring virtual machines for backup.
​
​Auto configuration
​

Manually configure virtual machines for backup

Customer action required: Phoenix CloudCache must be configured. For more information, see Configure Phoenix CloudCache.

Phoenix supports disaster recovery of virtual machines with Unified Extensible Firmware Interface (UEFI).

For more information, see DRaaS support matrix.

Customer action required: Upgrade Phoenix AWS proxy to version 4.9.1-101573 .

Phoenix DRaaS now supports the following:

For more information, see DRaaS support matrix.

Customer action required: None

You can now perform a file-level restore of Btrfs filesystem (Linux).

For more information, seeSupport matrix.

Customer action required: None

We're working relentlessly to enhance your product experience. So, we have redesigned the Cost Allocation page that has an intuitive user interface to let you accomplish tasks with ease.

For more information, see Cost Allocation.

The user interface for managing Administrative Groups is revamped for easier operations.

For more information, see Manage administrative groups.

Customer action required: None

The user interface for managing Activation Tokens is revamped for easier operations.

For more information, see Manage activation token.

Customer action required: None

The List all content rules API is enhanced wherein, the NAS rule structure returns content rule information.

For more information, see List all content rules.

Customer action required: No action required.

We are excited to announce that Phoenix is now a Federal Information Processing Standard (FIPS) 140-2 compliant data protection solution in theAWS GovCloud(US).FIPSincludes publicly announced security standards developed by the US Federal Government for computer systems used by non-military government agencies and government contractors.

The FIPS Publication 140-2 is a US Government standard that defines minimum security requirements for cryptographic modules in systems/services as per Section 5131 of the Information Technology Management Reform Act of 1996. The FIPS 140-2 standard is published by the US National Institute of Standards and Technology (NIST) and outlines the requirements that federal agencies and departments must adhere to when using technology that uses cryptography for transmission and storage of their data.

The Cryptographic Module Validation Program (CMVP), is a joint effort of NIST and the Canadian Center for Cyber Security (CCCS). CMVP validates cryptographic modules to meet the requirements for the Cryptographic standard (FIPS 140-2) and related FIPS cryptography standards. The FIPS 140-2 security requirements cover 11 areas related to the design and implementation of cryptographic modules.

Government agencies and contractors that must adhere to the FIPS 140-2 cryptographic standard now have the ability to meet the technology requirements for running sensitive workloads in the Phoenix GovCloud.

Druva’s end-to-end FIPS support within GovCloud offers:

Customer action required:Ensure that the version of the Phoenix agent deployed in the GovCloud is upgraded to 4.7.7 or later.

Phoenix now supports the backup and restore of files and folders, and NAS shares on Oracle Linux 7.8. For more information, see Support matrix.

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

The following features are scheduled to get released on October 19, 2020:

Starting 19th October 2020, when you configure your virtual machines for backup, you can select local storage to store backups locally by mapping a Phoenix CloudCache.

► The option will be available when you create or edit an auto-configuration rule or manually configure or reconfigure virtual machines for backup. (Click to expand)

Auto configuration rules

Manual configuration

Customer action required: Phoenix CloudCache must be configured. For more information, see Configure Phoenix CloudCache.

Starting 19th October 2020, you can restore databases from application-aware backups without requiring to restore the entire virtual machine. You can restore the database to its original location or an alternate location. You can also restore just the database files from a snapshot.

Also, when you perform a full VM restore, of MS SQL virtual machines (application-aware), the restored databases will be application-consistent.

📝 Note

​ This enhancement is only applicable to VMware on-premises as the NFS datastore is not supported by VMware cloud.

Customer action required: Deploy a fresh additional backup proxy and provision a Windows staging virtual machine.

When the source virtual machine (MS SQL) is backed up, Phoenix takes VSS snapshots of the drives where the database files reside and then backs up the entire disk attached to the source virtual machine. These disks (vmdk files) are then uploaded to Phoenix Cloud.

Now while restoring, because VSS is a proprietary feature of Windows, a Windows virtual machine (staging) is required to read the disks. A staging virtual machine is used to mount the selected vmdk files to the staging virtual machine from where Phoenix reads the SQL data for restoring to the target virtual machine.

The Windows staging virtual machine should meet the following criteria (Click to expand)

📝 Note
​

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

You can now filter MS-SQL server jobs to see all Full, Differential, and Transaction Log SQL backups. You can also use the All Backups filter to view all your MS-SQL backups.

For more information, see View jobs page and Jobs Filters.

Customer action required: No action required.

Phoenix now gives you an insight into the cogent lifecycle of credit utilization during the contract term. Phoenix simplifies the credit management process by:

For more information, see Credit term.

Note: Customers who have onboarded with the new contract type can view the credit term on the Dashboard page, the Analytics page, and on the My Accounts page. However, the credit term doesn't apply to customers who are still in the non-term contract.

Customer action required: No action required.

The List all backup proxies API is enhanced wherein, the backup proxy pool structure returns backup proxy pool name and time zone information.
For more information, see List all backup proxies.

Customer action required: No action required.

When a virtual machine configured for backup is deleted from the VMware environment, the first backup job after the virtual machine deletion fails. However, the virtual machine is disabled from backup to avoid subsequent job failures. The virtual machine that is disabled for backup will be still available for restore.

For information see, Delete a virtual machine configured for backup.

Customer action required: No action required.

Regardless of where customers run their VMware infrastructure, their data is comprehensively protected and always available with Druva Cloud Platform.

Customer action required: No action required.

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, alerts, and insight into the performances of 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.

Adding NAS shares just got easier! Phoenix now discovers NFS and SMB shares on a NAS device automatically as soon as you add the device in Phoenix. You can also run a share auto-discovery on-demand.

For more information, see Add a NAS share

Customer action required: Upgrade the NAS proxy to version 4.8.16-98358.

Druva Phoenix now backs up databases on Microsoft SQL Server 2019 inside a virtual machine using the Microsoft VSS and SQL Writer service.
Phoenix requires virtual machine credentials to perform application-aware backups.

Customer action required:Upgrade to the latest version (4.8.16-98404) of the Phoenix agent.

The newly redesigned NAS page in Phoenix has an intuitive user interface that lets you accomplish critical tasks with ease. Some of the key highlights of the new user interface are:

New Add NAS Proxy page

The new Add NAS Proxy page allows you to check prerequisites, download, install, and activate the NAS proxy from one single place.

New Add Device page

The new Add Device page allows you to configure your NAS device and map it to registered NAS proxies. Share auto-discovery discovers NFS and SMB shares. If you select the Use device credentials for auto-discovered shares option, Phoenix assigns device credentials to auto-discovered SMB shares.

New Create Backup Set page for NAS shares

The new Create Backup Set page allows you to configure everything that you need to create a backup set for a NAS share from one single place.

New NAS share details page

The redesigned NAS share details page lets you see all the configured backup sets for the NAS share at a glance. You can view more details about the configured backup sets, add new backup sets, or restore data from this page itself.

A new Restore Files page

The new Restore Files page gives you a snapshot viewer where you can select the type of snapshot and the restore point from which you want to restore data. You can search for the files to be restored or browse the folder hierarchy for them. You can also restore files across multiple folders or directories.

A new Jobs page for NAS

A new Jobs screen lets you see all your NAS jobs within the NAS page. You can also see the job details and logs.

The NAS workload now integrates with the credential store. Credentials are required to protect SMB shares. NFS shares do not need credentials.The Credential Store stores share-specific credentials that can be reused by other NAS shares on the device. The Credential Store also stores NAS device credentials. The credentials are validated while adding a NAS device mapped to a Windows proxy. The credentials updated in the Credential Store apply to all shares that use those credentials.

Small file backups in File Server and NAS are now 15% faster over low latency networks and up to 52% faster over high latency networks.

For more information, see:

Customer action required: No action required.

Incremental NAS backups are now up to 3x faster for data sets with low change rates.

Customer action required: Upgrade the NAS proxy to version 4.8.16-98358.

The Phoenix user interface for VMware workload is redesigned to help you perform critical tasks with ease. Key workflows such as deploying backup proxy, configuring VMs for backup, and restoring data are simplified. Following are some of the key enhancements:

Centralized Backup Proxy management

A common page to deploy additional backup proxies, create a proxy pool, and upgrade all backup proxies at one time.

Configure your virtual machines for backup with ease

Dedicated pages for manual and auto-configuration for virtual machines.

Centralized virtual machine management

A common page to perform all the tasks related to managing configured virtual machines.

Click on a configured virtual machine to view its configuration summary and backed up snapshots details.

Simplified restore experience

Intuitive restore workflows for virtual machines (non-application aware) and Microsoft SQL Server (application-aware). Also, now you have a tree view to select your data across folders and restore.

Customer action required: No action required.

We are glad to announce the following enhancements scheduled for August 17, 2020.

The Phoenix user interface for NAS workload is redesigned to help you perform critical tasks with ease. Key workflows such as adding a NAS device, adding a NAS proxy, creating backup sets are simplified.

Also, when you have a large number of shares, you need not add them manually. Phoenix automatically discovers shares on the NAS device as soon as you add it. You will also be able to run share auto-discovery on demand.

Customer action required: To use the auto-discovery feature, upgrade the NAS proxy to the latest version.

The Phoenix user interface for VMware workload is redesigned to help you perform critical tasks with ease. Key workflows such as deploying backup proxy, configuring VMs for backup, and restoring data are simplified.

Phoenix now gives you an insight into the cogent lifecycle of credit utilization during the contract term. Phoenix simplifies the credit management process by displaying the credit term (contract period) along with the credit balance on the Phoenix Management Console.

For more information, see Credit term.

Note: Customers who have onboarded with the new contract type can view the credit term on the Dashboard page, the Analytics page, and on the My Accounts page. However, the credit term doesn't apply to customers who are still in the non-term contract.

Customer action required:No action required.

Phoenix can now back up and restore virtual machines created and managed by Hyper-V on Windows Server 2019. For more information on the certified versions, see System Requirements for Hyper-V.

Customer action required: Install the latest Phoenix agent on the Hyper-V host on Windows Server 2019.

Druva Phoenix now lets you backup and restore the following link file system objects on Windows File Server and NAS Shares. This feature was previously supported only on Linux.

📝 Note

​Phoenix backs up only the link files and not the file or directory they point to.

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

You can now register your VMware setup with Phoenix in a jiffy using the Druva Proxy Deployer utility. You no longer need to deploy the OVA templates manually. Simply download the Druva Proxy Deployer utility from the Phoenix Management Console on your local system and the utility will guide you through the backup proxy deployment process.

Watch the video for the new simplified deployment experience.

For more information, see Deploy the first backup proxy and register the VMware setup.

Customer action required:No action required.

You can now protect vCenter version 7.0 and standalone ESXi host version 7.0.

Customer action required:If you are using vSphere version 7.0 or planning to upgrade, you need to redeploy the backup proxies from the Phoenix Management Console. For more information see, Deploy additional backup proxies.

The format of the startTime and endTime parameters for queued and running jobs is now fixed and in line with job statuses in the Jobs APIs.

This cloud update has minor bug fixes.

Phoenix now provides scripts to back up data files and the archived log files of Oracle standalone instances, separately.

For more information, see:

Customer action required:

Phoenix backups failed on the non-VSS partitions such as FAT, FAT 32, and exFAT.

You can now deploy multiple backup proxies in a single workflow from the Phoenix Management Console. The proxy deployment process is simplified in a way that:

For more information, see Deploy additional backup proxies.

The following GIF image demonstrates the enhanced user interface:

Customer action required:Upgrade the backup proxy to version 4.8.14-93097. You can download the VMware backup proxy from the Downloads page.

With this release, the backup pools are associated with a data center. This association helps you efficiently load balance your geographically distributed data centers and associated clusters.
For more information, see Backup proxy load balancing.
The following GIF image illustrates the association:

The following GIF image demonstrates the enhanced user interface:

Customer action required:Upgrade the backup proxy to version 4.8.14-93097. You can download the VMware backup proxy from the Downloads page.

Phoenix now supports the backup and restore of additional file attributes for CIFS/SMB, Linux and NFS shares. The supported attributes are:

CIFS/SMB shares

Linux and NFS shares

For more information, see:

Customer action required: Upgrade the Phoenix agent to the latest version, 4.8.14-93097.

Druva Phoenix now provides enhanced Jobs APIs to help API users gain more insight into the job details and to easily integrate APIs with the BI tools.

The API enhancements include:

To know more about Jobs APIs, see https://developer.druva.com/docs.

Druva is excited to announce the release of APIs for Phoenix GovCloud customers, which are now available on developer.druva.com. GovCloud customers can use these APIs to create reports and get insights into the jobs and their data. These APIs are authenticated using OAuth 2.0 access token, which is the most secure and popular authentication mechanism for APIs.

The following APIs have been published with this release:

Customer action required: No action required.

We have made some design changes and improvements to show real-time data for Jobs APIs.

To know more about Jobs APIs, see https://developer.druva.com/docs

Druva Phoenix now gives you the option to restore the latest version, all versions, and specific versions of file server and NAS files selected through backup set search. You can now select single or multiple files from the search results for restore. Depending upon the selections, some or all of these options are available.

For more information, see:

Customer action required: No customer action is required.

You can now select the operating system of the file server and download the respective Phoenix agent from the Phoenix Management Console itself while registering the server.

For more information, see:

Customer action required: Update the Phoenix agent to the latest version4.8.13-91382.

Druva Phoenix allows you to assign credentials to Windows Servers and MS-SQL Servers. When you assign a credential to a server in the Phoenix Management Console, Phoenix automatically assigns it to the Phoenix service on the Windows file server, and this credential persists through agent upgrades. If you update an old credential in the credential store, it automatically updates that credential for all servers which were using that credential. The Phoenix agent service running on those servers is assigned the updated credentials as well.

You can manage these credentials from the Registered Servers screen under the Windows/Linux servers page. The Credentials column displays the credentials assigned to each server and their validation status. The Manage Credentials functionality allows you to:

Customer action required: Update the Phoenix agent to the latest version4.8.13-91382.

With this release the following rights are customizable when you create custom roles:

Also, a new customizable right is added for DRaaS:

For more information see, Manage administrator roles.

Customer action required: No customer action is required.

With this release, the Cost Allocation Report and Credit Limits will account for LTR savings.

The Cost Allocation Report gives you granular details of the credits consumed and accounts for LTR credit savings over the month. This report shows historical data for 12 months.

To know more, see:

Customer action required: No action required.

The following table lists the versions of the agents released:

Druva is excited to introduce Realize Storage Insights and Recommendations services that help customers optimize their storage utilization costs. Built on top of Druva Phoenix - these insights are available for File Server and NAS data sources.

Realize Storage Insights:Primarily designed to provide customers visibility into their data under protection, Storage Insights enables customers to gain insights into non-critical business data and take the required actions to exclude it from backup and thus, optimize their storage costs. It enables administrators to:

To learn more, see Realize Storage Insights.

Recommendations:A smart service designed to identify and proactively inform administrators about the storage utilization costs on the non-business critical data under protection and recommend necessary action to exclude it from backup and save costs. It enables administrators to:

To learn more, see Recommendations.

Customer action required: No user action is required.

❗ Important

Realize Storage Insights and Recommendations services are available at no additional cost for Phoenix customers with Elite and Enterprise License and enabled by default for File Server and NAS data sources that are under protection.

With this release, Druva is excited to announce support for Microsoft SQL Server 2019 with Druva Phoenix. You can now protect SQL Server 2019 databases with Phoenix.

Customer action required: Upgrade to the Phoenix agent version 4.8.12-90434, if already upgraded to SQL Server 2019

Knowing and understanding your credit consumption with Druva is an important step towards using our products efficiently. With this thought, we’ve introduced a new report called the Credit Consumption Report that you can view, download, and subscribe to on a monthly basis.

The report’s duration is set as the last 12 months by default and it shows details such as:

For more information, see Credit Consumption Report.

Customer action required:No user action required

The newly redesigned Windows/LinuxServers page in Phoenix gives you a modern user interface that is intuitive and lets you accomplish key tasks in fewer clicks. Some of the key highlights of the new user interface are:

New Configure Backup for Selected Servers page

The new Configure Backup for Selected Servers page allows you to configure everything that you need to create a file backup set in one single place.

A new server details page

The redesigned server details page lets you see all the configured backup sets for the server at a glance. You can view more details about the configured backup sets, create new backup sets or restore data from this page itself.

A new Restore data page

The new restore data page gives you a snapshot viewer where you can select the type of snapshot and the restore point from which you want to restore data. You can search for files to be restored or browse the folder hierarchy for them. You can also restore files across multiple folders or directories.

A new jobs page for file servers

A new Jobs screen lets you see all your file server jobs within the Windows/Linux servers page. You can also see the job details and logs.

For more information, see:

Customer action required: No user action required.

Phoenix now supports file-level restore to a virtual machine in VMC. For more information, see File level restore (VMware).

The following table lists the versions of the agents released:

Are the VMs in your environment DR ready? Find out this and more as Phoenix automates this process for you with a Prerequisites check capability. When the VMs are being backed up, the prerequisites check process kicks into action and provides a status if the VMs are DR ready or not.

By validating the readiness of your VM environment for failover, you can validate and test your DR strategy and avoid surprises during failover. This DR feature can also lower the cost of testing by reducing failed requests to the cloud.

The status of the failover prerequisite checks is available through the Virtual Machines page.​​​​​​

For more information, see DRaaS failover prerequisite checks.

Customer action required: Upgrade the backup proxy to version 4.8.11-87483 . You can download the VMware backup proxy from the Downloads page.

The following video provides more insights about the failover prerequisite check capability.

You can now choose to failback all or multiple VMs from a DR plan in one step. This is easily accomplished by selecting the instances you want to failover from your list of failover instances. The VMs selected for failback are listed under one job in the failover job details page.

This enhancement makes the failback process faster and reduces overhead for any system administrator helping them to bring their business back to the production environment.

Customer action required:To initiate failback, select instances from the Failover instances console.

For more information see, Manage disaster recovery failback.

The following video highlights the value of the enhancement, what aspect of the product is enhanced, and where you can find more information.

Druva Phoenix now allows you to assign credentials to Windows Servers and MS-SQL Servers. When you assign a credential to a server in the Phoenix management console, Phoenix automatically assigns it to the Phoenix service on the Windows file server, and this credential persists through agent upgrades.

You can manage these credentials from the All Servers tab under the Windows/Linux server page. A newly added Credentials column displays the credentials assigned to each server and their validation status. The Manage Credentials functionality allows you to:

Customer action required: Upgrade to the latest version of the Phoenix agent, 4.8.11-87541.

Druva Phoenix now allows you to enter the wildcard character Asterix ( * ) in the Include pattern field while creating a SQL backup set. This pattern backs up all databases that currently exist on the SQL instance and those that will be added in the future. You need not select Database Names manually if you’ve entered * in the Include pattern field.

For more information, see Manage backup set and Configure MS-SQL instance or AG for backup.

Customer action required: Upgrade to the latest version of the Phoenix agent, 4.8.11-87541.

For each instance you want to failback, you can:

Customer action required:When you launch failback, provide the EC2 credentials in the Failback Settings page.

For more information see, Manage disaster recovery failback.

You can specify a prefix or a suffix for VM's name you want to failback. This helps you to identify the VMs that were failed back.

Customer action required:When you launch failback, provide the VM Name (Prefix / Suffix) in the Failback Settings page.

For more information see, Manage disaster recovery failback.

For ease of management of DR plans, the UI is enhanced to allow you to select a specific DR plan from the DR plan drop-down list. Also, the underlying tasks are displayed in a modular way as illustrated in the following screenshots.

For more information, see Manage disaster recovery plan.

Now while restoring your virtual machines to an alternate location, you can rename your virtual machines. This capability is available for a full restore of virtual machines and application-aware restores (currently involves restores of full VM).

For more information see, Restore VMware virtual machine to an alternate location.

The Recovered VM Name option is added.

While restoring your virtual machines to an alternate location, you will now receive an alert if there is insufficient free space on the destination datastore.This capability is available for a full restore of virtual machines and application-aware restores (currently involves restores of full VM).

For more information see, Restore VMware virtual machine to an alternate location.

The alert is displayed with the Available space field.

The following table lists the versions of the agents released:

Druva Phoenix now supports two new categories of file types that you can include in or exclude from your backups for Windows/Linux servers and NAS.

For more information, see About Phoenix for File server and About Phoenix for NAS shares.

No user action required.

Druva Phoenix introduces access controls for effective and secured utilization of Druva APIs in your organization. While generating API credentials on the Druva Cloud Platform, Druva Cloud Administrators can now assign API accesses to inSync cloud administrators and Phoenix cloud administrators including view-only cloud and custom cloud administrators.

For more information, see Apply authorization restrictions.

With this release, the integration of the ServiceNow app with Druva helps you automate the ticket creation workflow for Druva Phoenix backup failures. Now, get quick updates using the Druva ServiceNow app about any failed backup activities within Phoenix without the need to log in to the Phoenix Management Console or waiting for an email.

Key features

This release brings an enhanced version of the Phoenix agent for File Server. We have added new, client-side architectural changes that significantly improve the backup and restore throughput.

Performance improvement observed during the internal tests performed:

Customer action required:To experience the enhanced performance, contact Druva Support.

The following table lists the versions of the agents released:

This release brings an enhanced version of the Phoenix agent for Microsoft SQL Server. We have added new, client-side architectural changes that significantly improve the backup and restore throughput.

Performance improvement observed during the internal tests performed:

Customer action required:We recommend you to upgrade to the latest version of Phoenix agent to experience the performance improvement. The system requirements to run the latest version of Phoenix agent are:

This release brings an enhanced version of the Phoenix NAS agent. We have added new, client-side architectural changes that significantly improve the backup and restore throughput.

Performance improvement observed during the internal tests performed:

Customer action required:We recommend you to upgrade to the latest version of Phoenix agent to experience the performance improvement. The system requirements to run the latest version of Phoenix agent are:

The following table lists the versions of the agents released:

You can now restore the databases associated with VMware virtual machines with static IPs.

Customer action required: During restore, assign a different IP address for the destination VMware virtual machine.

For more information, see Restore Microsoft SQL Server databases on VMware virtual machines.

This release brings an enhanced version of the Phoenix NAS agent. We have added new, client-side architectural changes that significantly improve the backup and restore throughput.

Performance improvement observed during the internal tests performed:

Customer action required:We recommend you to upgrade to the latest version of Phoenix agent to experience the performance improvement. Here is what it takes to upgrade to the latest version of Phoenix agent:

The upcoming Phoenix release will bring an enhanced version of the Phoenix agent for File Server, MS-SQL, and Hyper-V.

Customer action required:

Here is what it takes to upgrade to the latest version of Phoenix agent:

Warning: Upgrades and new installations of the File Server, NAS, MS-SQL, and Hyper-V agents will be blocked from January 20, 2020,onwards ,for systems that do not meet the minimum system requirement.

With this release, Phoenix provides you the ability to backup and restore files and folders on Oracle Linux 7.7. Moreover, you can also deploy NAS Proxy on Oracle Linux 7.7. For more information, see the support matrix.​​​​​​

Customer action required:No action required

With this release, Phoenix makes it easier for you to view the list of files that have been skipped from the backup. The log folder contains a new ‘Phoenix-<JobID>-MissedFiles.log’ file that lists the skipped and missed files during a backup.

The following table lists the versions of the agents released: