Clumio provides a secure way to protect your DynamoDB assets using SecureVault Backup and Snap protection policies. SecureVault Backups are stored within Clumio's air-gapped and immutable storage, providing maximum security for your data. Snaps are point-in-time backups (snapshots) of your DynamoDB tables and are stored in the same location as your tables.

Clumio leverages AWS’s DynamoDB backup and provides a single window from which to apply protection policies to tables across all accounts and regions.

A Clumio policy determines the backup frequencies and retention periods for the DynamoDB tables that it protects. The hourly backup frequency (hourly refers to the time interval at which a backup is generated) is required when you create a SecureVault Backup policy for DynamoDB tables.

The DynamoDB tables page AWS > Protect> [Account] > DynamoDB tables lists all of the DynamoDB tables deployed on the connected AWS account, regardless of whether the volumes are protected by Clumio or not.

The DynamoDB tables page is filtered by Active tables by default and displays the following information:

  • Table name: The name of the table
  • Tags: The AWS tag key and value assigned to the table. A tbale can be assigned multiple tags.
  • Policy: The Clumio policy that is currently protecting the table.
  • Compliance status: The compliance status. The asset can be in one of the following statuses:
    • In compliance: The asset is compliant with its protection policy; all recurring backups and snapshots within the last 7 days have successfully completed.
    • Out of compliance: The asset has fallen out of compliance with its protection policy either due to backup or snapshot issues encountered in the last 7 days or because there were no successful backup since the last attempt. An asset falls out of compliance when it exceeds its assigned policy’s recovery point objective (RPO) without a successful backup or snapshot.
    • Waiting for seeding: The asset was recently assigned to a new policy, and the asset is currently waiting to establish compliance under the new policy.
    • Seeding: The asset was recently assigned to a new policy, and the asset is currently establishing compliance under the new policy is in progress. Once seeding successfully completes, the “Last Backup” status changes to the number of days since the last successful backup occurred.
    • Deactivated: The asset's policy was deactivated. As a result, all of the policy’s tasks, including scheduled backups and snapshots, are not running.
  • Last backup: The details for the last successful backup. The last backup column displays the following details.
    • # of hours/days: The length of time since the last successful backup occurred. If the asset was recently assigned to a new policy and is waiting for seeding, the # of hours/days represents the last successful backup taken under the old policy.
    • Dash symbol (-): There are no backups for this asset because a successful backup was never taken.

Click a DynamoDB table name on the Active DynamoDB tables page to view its attributes, backup history, restored files, and active alerts. The protection history calendar displays the dates with available backups and Snaps. Refer to the legend below the calendar to see what types of backups are available for that month.