We are excited to announce enhancements to the restore workflow for EC2 backups and EBS snapshots to ensure secure access to your restored instances and enhanced flexibility in managing encryption keys.

Experience greater flexibility in selecting your SSH encryption keys, with better access control to manage keys across multiple AWS accounts. With enhanced support for cross-account key usage, you can now seamlessly restore air-gapped backups of your EC2 instances and EBS volumes, even when the source volumes were unencrypted at the time of backup.

For more information, see Restoring AMIs and Restoring EBS Snapshots.

With Azure Storage integration, you can now select your preferred Cloud Storage on Azure or AWS cloud ecosystems, depending on your business requirements.

Key benefits

📝 Note

Azure Storage is currently supported within the East US Region. All existing backups will remain in your chosen Cloud Storage depending on the Storage Rules defined and the backup configuration.

Customer action required: To sign up for this feature and configure Azure Storage, contact your Account Manager.

❗ 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.

Archived Release Notes 2023

Archived Release Notes 2022

Archived Release Notes 2021

Archived Release Notes 2020