❗ Important

This capability is supported only for Airgap Backup of EC2 and EBS resources.

We’re excited to introduce Threat Hunting, a powerful new feature that enhances the security posture and assists in improving security operations and incident response workflow.

Our comprehensive approach lets you actively search for and address threats hiding in your backed-up data. With Threat Hunting, you can quickly isolate, analyze, and neutralize threats, stopping infections from returning to your production environment.

Threat Hunting helps you have a unified view of threats—and you can define the scope of resources, adjust scan depth, set IOC parameters, and even decide how often to run threat hunts, whether proactively or on-demand. Here’s what you can expect from this latest update:

Customer action required:

For more information, see Get Started with Threat Hunting.
​

You can now create an AMI exclusively for the root volume, along with the corresponding complete snapshot, and manage the backup definition all within a single backup policy.

Manage your EC2 backup configuration with enhanced options to enable backup of root volumes only, or both root and the data volumes. With this increased control, you could avoid the backup of the large data volumes, particularly for non-critical data. For more information, see Manage Backup Policies.

While you experience the speed and power of Druva’s 100% SaaS cloud-first data protection platform, we are committed to ensuring that your entire journey with us is as seamless as possible. So, here’s introducing the Druva help center; a self-serve-first help experience that offers quick access to assistance whenever you need it. The new help center functions as the primary repository for all information, delivering a significantly more personalized and contextual experience when accessed through the product console.

Here’s a look at what’s new and what’s changed:

Customer action required: We have ensured that the transition to help.druva.com is seamless for you. We recommend that you update your bookmarks, and ensure you're using the latest agent versions for Enterprise Workloads.

Go ahead and explore the enhanced experience or learn more.

With the file-level recovery functionality, you can initiate a recovery instance within Druva’s environment and choose the files you want to recover. The instance launches and runs Druva's FLR agent, which virtually mounts the chosen point-in-time backup and serves a browsable view of files and folders. Initiate a restore of specific files, which will remain accessible via the S3 bucket in your source AWS account.

For more information, see Restoring Point-in time Backups with File Level Recovery and Restoring AMIs.

You can now create an AMI exclusively for the root volume, along with the corresponding complete snapshot, and manage the backup definition all within a single backup policy.

Enable the Root volume only AMI with each backup within your AMI Options to create a second AMI for all EC2 instances backed up by the policy, with the Block Device Mappings adjusted to only contain the root volume. For more information, see Manage Backup Policies.

📝 Note

This feature is available only when AMI is selected within AMI Options, flagging this as an AMI policy.

You can now select the EC2 Instance Metadata Service (IMDS) version when restoring instances from an AMI or snapshot. The IMDS version on the original instance will determine the version available when initiating restore (IMDSv1 or IMDSv2). For more information, see Restore to an Instance.
​

The end-to-end reporting functionality allows administrators to generate and customize reports to monitor data protection across AWS accounts.

With this enhancement, administrators with Admin View or read-only access can also generate and download reports from the management console.

For more information, see Reports.

You can now protect virtual machines deployed in Azure Cloud. Experience seamless and secure onboarding of Azure subscriptions to Druva with an agentless, cloud-native SaaS solution that ensures secure air-gapped backup of Azure VMs, while significantly reducing storage costs.

The data protection solution leverages Druva's backup and restore solution for end-to-end protection of Azure VMs and managed disks over Druva storage. Druva also protects Azure VM data from ransomware by creating an encrypted backup copy of your data in Druva's Cloud, that is inaccessible to attackers. For more information, see Backup and Restore Azure Virtual Machines.

Customer action required: Contact your Account Manager for more information.

Here's a sneak peek:

The EC2 Storage and Credit Consumption report offers insights into the backup-wise storage and credit consumption for individual EC2 resources in an organization.

With the enhanced reporting capability, you can now specify AWS Tags as part of the report definition criteria. Tags are key and value pairs that act as metadata to help identify and organize your AWS resources. Based on the Key selected, you may specify the appropriate Value to generate the report. The enhanced report will now also include information on the AWS Account associated with the organization for which the report is generated. For more information, see EC2 Storage and Credit Consumption Report.

Here is a preview of the Report

Multi-account onboarding via AWS Control Tower will now be unavailable from your Native Workloads management console.

What's Next: If you currently use the feature, you may transition to the native AWS StackSet, which offers enhanced account provisioning and automated template management, ensuring seamless multi-account management.

AWS StackSet is a powerful tool that delivers functionality similar to AWS Control Tower, while offering a more dynamic and customizable approach to multi-account management. For more information, see Configure Multiple AWS Accounts.

No immediate action is required. If you have questions on the deprecation, contact Support.

The backup schedule for a policy enabled to backup data to Druva Cloud can be set to an hourly frequency or higher. Policies enabled for backup to Druva Cloud will now be executed at a minimum frequency of an hour.

When updating an existing policy to backup data to Druva Cloud, a validation displays if the backup frequency is lower than an hour. For more information, see Manage Backup Policies.

You can now view and download the list of resources identified as part of Resource Rules within a backup policy. You may use the search or filter feature to locate specific resources by Resource Type or Region.

If the resource rules defined filter duplicate resources, the duplicate rule will be labeled by a warning icon on the management console. You can still create rules that identify duplicate resources, but these will be flagged, and you may choose to edit the rule as appropriate.

For more information, see Specify Resources for Backup.

The EC2 Storage and Credit Consumption report offers insights into the backup-wise storage and credit consumption for individual EC2 resources in an organization. The report provides information on consumption at the resource level, with associated details on backup and disk usage, estimated credit consumption, and the LTR savings within the chosen period.

With a granular view of the following data aside from the status of each storage consumption job run for each resource, you may analyze your consumption and initiate appropriate action:

For more information, see Reports.

Druva has deprecated support for Kubernetes data protection on AWS Workloads. Starting March 1 2023, you can no longer protect Kubernetes clusters and application groups. There is no impact on your existing backup policies and retention configured for other AWS resources.

Customer action: No action is required from your end post this deprecation.

With Long Term Retention, you can now leverage Druva’s AWS Deep Archive for EC2 backups using a simplified, policy-based solution to automatically move backed-up data to the cold tier. Configure LTR for EC2 to better manage your enterprise storage requirements as well as optimize TCO.

❗ Important

Long Term Retention is currently available only on policies configured to backup EC2 and EBS snapshots to Druva Cloud.

You may configure Long Term Retention (LTR) on backup policies with the LTR-eligible retention period. A one-year retention is required before you can go ahead and enable LTR for EC2. Once enabled, you can continue to monitor savings via LTR, and restore snapshots from the cold tier.

📝 Note
​ The availability of the Long Term Retention (LTR) feature is limited to Enterprise and Elite editions. To access this feature, contact your Druva Account Manager or Support.

For more information, see Long Term Retention. Have more questions? Refer to the LTR FAQs.

You can now filter the backup jobs based on whether they were executed manually or based on a policy-based backup schedule.

The Generated filter allows you to select backup jobs initiated Manually or By Policy. If you select By Policy, proceed by selecting a backup policy to filter associated jobs. The Policy Name column displays the appropriate backup policy for jobs generated automatically. For more information, see View Jobs.

Use the Association functionality to create an association between resources as a copy or a replacement of the original instance. You can now Restore EBS snapshots on Druva Cloud to an instance using Associations. When you restore snapshots using Associate as A Replacement, you may also choose to add the restored instance to the original backup policy so it continues to be backed up based on the existing policy schedule.

For more information, see Restoring Snapshots to an Instance.

Archived Release Notes 2022

Archived Release Notes 2021

Archived Release Notes 2020

Archived Release Notes 2019