As April comes to its conclusion, we take a breath to look back at what we have achieved in 2021 to date. This past year, a full year with the backdrop of the global pandemic, Druva’s product and engineering teams have been working around the clock to deliver a number of new features and improvements to help organizations better protect and recover workloads in their native AWS cloud environments. As our blog regulars know, here at Druva we are very proud of our “Data protection for the cloud era” mantra. Our 100% SaaS model helps to differentiate us from legacy software product updates, as we can deliver not just new functionality, but improved user experiences on a monthly basis, without the baggage of patching or hardware upgrades.
This is the third blog in the What’s new series, so please take time to check out the previous posts, as we summarized the latest updates to Druva’s data center workloads portfolio, and updates for multi-geo residency in Microsoft 365 backup. This edition features enhancements for cloud-native workloads on AWS, and is organized into three categories — simplicity-experience, workloads-scale, and security-resiliency.
Simplifying the user experience
New organization selector on the Druva console
One of the big benefits of using Druva is that we bring our customers the added benefit of reducing complexity of data protection at scale. That is why we were excited to confirm that Druva now brings to you the option to access multiple organizations and AWS accounts from within your console. You can now easily select your chosen organization from the top navigation bar in the console.
New organization selector on the Druva console for managing AWS workloads.
Once selected, the account drop-down on the left navigation will display all aws accounts linked to that organization to which the user is granted access. This is a huge benefit to enterprise customers who may be managing hundreds of AWS accounts linked to different business units or customers.
For any organizations with no specific name defined in the Druva console, these will display as a default organization. From here, any administrators can choose to update the organization name from the organization settings page. It is recommended that you assign unique organization names to avoid multiple default organizations.
User interface enhancements
We made another enhancement towards the end of March 2021 where users can now experience a revamped user interface with workflow enhancements to ensure easier operations. The redesigned console for managing native AWS workloads offers an intuitive user interface with the navigation organized into both organizational and account-level configuration elements.
Here is a summary of what was released:
- Global navigation update: Quick access to manage and administer organization-level components across AWS accounts, from the top navigation bar
- Account-level administration: Enhanced left navigation menu to easily configure and manage your AWS resources, manage disaster recovery plans, and resource schedules at an account level
- Integrated resources and backups/restores: Easily manage AWS resources and configure your backups and restores across all resource types with our enhanced interface
- Integrated AWS accounts page: Easy administration of all AWS accounts within your chosen organization; add new accounts and manage AWS access and synchronization using the consolidated account listing page
There is no user action required to benefit from these enhancements; the migration will be managed by the Druva support team.
New access points: organization-level administration
Top navigation bar to manage and administer global components across AWS accounts.
Manage AWS resource types at an individual account level.
Scaling for user workloads
New policy-based archival of EBS snapshots to Amazon S3 storage
Enterprises often need to retain a long-term backup of data for business continuity, compliance, customer contracts, and eDiscovery. Storage optimization is an ongoing process of evaluating your data storage needs and choosing a cost-effective AWS storage option that meets business needs. However, AWS does not currently offer an out-of-box low-cost storage tier for EBS snapshots.
Druva now allows you to transition your Amazon EBS snapshots to Amazon S3 storage classes such as Amazon S3 Standard, Amazon S3 Standard-IA, Amazon S3 One Zone, Amazon S3 Glacier, and Amazon S3 Glacier Deep Archive, to significantly reduce costs while retaining long-term availability. In addition, this transition can be accomplished automatically via a standard backup policy.
Policy-based archiving of Amazon EBS snapshots to Amazon S3 offers the following benefits:
- Cost benefits: Transitioning snapshots to lower-cost storage offers significant savings on long-term retention
- Ease of use: Policy-based approach to transition Amazon EBS snapshots to Amazon S3 (and other storage classes)
- Recovery: Recovery of individual files or snapshots from Amazon S3
- File-level search in snapshots: Metadata-based file search to locate files from the snapshots, without having to recover snapshots in Amazon S3
New policy-based archiving of Amazon EBS snapshots to Amazon S3 storage tiers.
Manual archive of EBS snapshots to Amazon S3 storage
You also have the option to manually transition your Amazon EBS snapshots to Amazon S3 storage classes. This is a great option for backups that may be under management, but not part of any policy within your management console.
Manually archive Amazon EBS snapshots to Amazon S3 storage tiers.
Configuring SSO for Druva
Security is always a primary concern for Druva and our customers. So we are always looking at ways to support key security requirements. Single sign-on (SSO) is a popular security mechanism that allows users to access multiple resources using a single action of authentication and authorization. Druva supports SSO for administrators. By enabling SSO, administrators can access all Druva services without the need for a separate login.
Note: Single sign-on applies only to customers who also have existing product licenses.
- Integrated access across Druva services
- Reduced human errors
- Enhanced security with authentication tokens validating SSO attempts
- Reduced administration efforts with fewer password reset requests
For more information, read about configuring SSO in the Druva documentation portal.
Logging in via SSO
Simply log into the Druva console using your SSO credentials, and then use the global navigation panel to navigate Druva’s products and services.
Global navigation panel to navigate Druva’s products and services.
- If you are a Druva customer with SSO credentials, you will be directly logged into your account.
- If you currently do not have an active Druva CloudRanger license for AWS workload backup, you will be redirected to the signup page to create a trial account.
Note: Druva customers with no pre-existing credentials will continue to log in via their existing console.
For more information on configuring SSO for your organization, contact the Druva support team.
The Druva team is delivering new features and updates on a monthly basis. We are always listening to the needs of our customers and want to hear from you. If you’re not yet a Druva customer, hopefully this series (and future ones) will make clear one key aspect separating the Druva cloud from traditional approaches — your system is always updated without the headache of an upgrade cycle. Stay tuned for our next installment, featuring our products for ransomware protection and recovery.
This was a summary of new features and key updates. For a comprehensive list, read the release notes.