Commvault Unveils Clumio Backtrack - Near Instant Dataset Recovery in S3
Amazon DynamoDB is one of the fastest growing and most widely adopted databases in the AWS cloud. Due to its support for very high transaction volumes (20 million requests per second), it has become an important function of mission critical workloads in the cloud. Several large enterprise customers like Lyft, Airbnb, Redfin and we (Clumio) use it extensively to build production applications and deliver an ideal experience to customers. Since this database has critical persistent data, its protection has become necessary for all customers to ensure that they can recover from an outage or data loss incident.
Since Amazon DynamoDB is offered as a service, there are no manual scripts that customers can use to protect the database. To solve this issue, DynamoDB itself provides multiple options to ensure that customers can backup their database. DynamoDB provides Point in Time Recovery (PITR) configuration for all of its tables. When configured, customers can recover to any specific point in time in the last 35 days, depending on the PITR configuration. Additionally, DynamoDB allows customers to take a manual snapshot of the entire database so that customers can recover from that snapshot at any time in the future. This snapshot can also be used to achieve compliance with certain regulatory requirements that are enforced upon some industry verticals. However, while speaking to enterprise customers, we’ve heard them ask for following enhancements:
All of the customer conversations converged to demonstrate that customer’s require enhancements for key capabilities like ransomware protection, compliance visibility, granular recovery with low RTO, and built-in efficiencies to drive down costs. To help with these customer needs, we are excited to announce the newest innovation in the Clumio family with Clumio Protect for DynamoDB.
Similar to data protection of other AWS assets, the deployment of the solution is simple with a single pane of glass experience. The deployment is infrastructure-less and agent-less for all your AWS accounts via a Cloud Formation Template or Terraform. After deploying, you can see all your DynamoDB Tables across all your accounts. Next, you create a Policy with your required RPO configurations and easily apply that to one or all of your AWS accounts with the configuration of a simple Rule.
Policy allows you to define your business intent of configuring when to create backups and how long to store them in Clumio. You even get the option to configure On-Demand backup options and whether to keep the backups In region or a Specific Region of your choice. The Snap tab allows you to configure Operational Recovery operations like Point-In-Time recovery (PITR) and In-account snapshots.
With Protection Rules, you can easily extend the policy to any/every DynamoDB Table of your choice. You can protect your DynamoDB Tables either by Account, Region or Tags. With Tags, you also get the flexibility to configure specific tags, multiple tags, All of the tags or Tag Contains. This rule provides complete protection of Tables that are present not just today but also any future tables with appropriate tags.
While performing Data recovery, you can either recover from Clumio’s SecureVault Backups or from Clumio Snaps. If you have the PITR configured, you can also recover that or any previously taken snapshots for the DynamoDB Table, all from the same calendar view. With the intuitive interface, you get complete visibility into when backups were taken and whether any backup is missing from the view. While performing recovery from the SecureVault backups, you can either restore the entire DynamoDB Table or perform Granular recovery.
When performing Full recovery, you get the following choices:
While performing Granular recovery, you get the following experience:
You can specify a particular Partition Key along with an optional Sort Key. Add further filters in Advanced Options to be able to quickly preview the data that matches your specified filters. Results are automatically hidden to ensure data privacy, and the administrator needs to have access to a particular role in order to perform Granular Recovery.
In the next step, you can either directly download the data or even transparently share the data with another colleague inside the organization, or an auditor, to ensure compliance.