What’s new — Druva for hybrid workloads: VMware, cloud DR, NAS, and more

This is the first of four quarterly round-ups for new features and improvements in how the Druva Cloud Platform protects hybrid workloads. Whether you’re a current customer looking to receive a quick overview, or a new prospect looking to move to the leading cloud data protection platform, I hope you’ll find this round-up useful. We make all of our monthly cloud-push updates available publicly (can’t say that for other vendors), and in this blog we’ll be highlighting the new and notable ones. Of course, the beauty of a SaaS data protection model is that new features are automatically made available to you on a monthly basis — with no need to plan, manage, or test infrastructure updates. 

Between January and March 2021, we delivered new features across the following areas:

VMware and VMware Cloud

vCenter and ESXi migrations and upgrades happen for good reasons. You want your backups to work seamlessly after you migrate. Druva makes this step painless. In one step, your backups are ready for the newly migrated vCenter/ESXi host. You can directly map or change the IP/FQDN of the existing vCenter/ESXi host to the IP/FQDN of the new vCenter/ESXi you want to migrate from the Druva management console. 

Druva has also introduced a VMware proxy disconnect notification feature — to notify you of both a possible network problem, and to forewarn you about possible backup failures that could occur due to a disconnected proxy. Our proxy pooling provides scale and resiliency by allowing a pool of proxies to support backup operations. 

Druva is focused on ensuring that wherever customers run their VMware infrastructure, their data is comprehensively protected and always available. To that end, we have the following certification updates:

  • Druva is certified with every new version of VMware Cloud on AWS that is released quarterly. Druva’s latest certification is for VMware Cloud on AWS SDDC 1.14. 
  • Druva is also certified for backup and disaster recovery of VMware Cloud on Dell EMC.
  • Druva now supports vSAN 7.0 
  • Druva has expanded its VMware API functionality to return backup and restore details for SQL databases backed up on virtual machines. For more information, see our developer portal for APIs.

Cloud disaster recovery 

Cloud disaster recovery (DR) can be a transformative use case for customers because it can allow them to eliminate redundant infrastructure and costs, or simply enable a level of resiliency that did not previously exist. Our latest update allows customers to get failover and failback for Windows and Linux VMs using GPT disks (GUID partition table).

From a platform compatibility perspective, Druva now supports a new version of Oracle (Linux) for failover/failback (version 6.10. 7.9, 8.2) for both UEFI and BIOS. For more information, see the DRaaS support matrix.


Customers are increasingly shifting database workloads to the cloud. Often that process involves a “lift and shift,” or re-hosting of the database server on an AWS EC2 (or equivalent instance), regardless of the long-term migration plan. Druva’s direct-to-cloud (DTC) capability helps customers accelerate their cloud projects and confidently protect their data wherever it lives. Our Oracle direct-to-cloud is an expansion of our Oracle data protection capabilities which already serves both on-premises and cloud databases. Oracle direct-to-cloud recently became available for customers in an early release. It will be generally available in 1H 2021.

Microsoft SQL is the second most popular relational database in use (after Oracle). We’ve accelerated backup of SQL databases (incrementals) with support for Microsoft VDI for differential backups of SQL databases. 

Druva also delivered new enhancements for its agentless, app-aware backup/restore of SQL in VMware. These updates further simplify the user experience and include: 

  • Auto-discovery of SQL instances at restore time (eliminating manually entry)
  • More granular control to cancel restore jobs (while files are downloading or before they’re attached to the target database)


We’ve been delivering a torrent of new features and enhancements to our NAS capabilities over the last six months. These have been focused on both performance and experience. A key new feature is support for pre/post backup scripts for NAS shares. You may want to use pre- and post-backup scripts to perform tasks including:

  • Stopping an anti-virus service before the backup job and restarting the service after the backup completes
  • Backing up database dumps as flat files using the NAS agent, and then deleting the dump files after the backup completes
  • Changing permissions on files or servers before a backup, and resetting them after the backup completes

With these functionalities, users define and apply scripts at the backup policy level (see image below). Our documentation provides two sample scripts to help you better understand when and how to use this new feature.

A new enhancement is support for lowest level privileges when protecting SMB shares on NetApp filers. This is useful for situations where one account does not have all required permissions over all folders in the SMB share hierarchy on NetApp, and ensures both successful backups and restores. For more information, read the release notes.

Next steps

Druva started its new fiscal year in April, and I can tell you that we have a lot of great new capabilities in the pipeline. If you’re new to this blog series, I encourage you to explore the previous editions below, and visit the product section of the Druva blog.

If you have questions or suggestions for future updates, don’t hesitate to reach out to me via Twitter DM. For the full list of updates, read the release notes.

Druva surpasses $2 billion valuation as it defines tomorrow’s data protection | Learn more sticky-promo-icon-carrot