DynamoDB policies

A DynamoDB policy at Clumio defines when a SecureVault Backup or Snap should be generated and how long that Backup or Snap should be retained. The same policy can be used to configure SecureVault Backups and Snaps.

SecureVault backups are complete standalone copies of your DynamoDB tables. The backups are saved remotely to Clumio and retained for the length of time specified in the protection policy. Clumio enforces an hourly SLA to ensure successful SecureVault backups. This means whichever backup schedule you select, the hourly backup schedule is enforced by default. You can perform a full restore of your tables or a granular record retrieval from a specific table from a SecureVault backup.

Clumio-managed AWS snapshots are taken by AWS, stored in your AWS account, and retained for the period you configure in the protection policy. If you later make changes to these frequency and retention settings from the AWS management console, these changes will override the selections you made on the Clumio platform. You can restore a snapshot up to a specific point in time within the retention period for continuous backups, or from a specific snapshot, from any unexpired backups.

DynamoDB protection policies are created from the Backup policies page. Protection policies are effective as soon as you create a protection rule to apply the protection policy. Clumio creates a seeding backup the very first time the DynamoDB tables are backed up. All subsequent backups are incremental.

Before you activate protection for your DynamoDB tables from Clumio, you must first connect to your AWS environment through Clumio, see AWS account connection.

You can configure a single CLumio policy to protect all the different assets you have connected to Clumio. For example you can create a policy to protect AWS EBS volumes, RDS databases, DynamoDB tables, M365 assets, and VMware VMs. The tasks below describe details specific to DynamoDB.

Creating a DynamoDB SecureVault policy

  1. Navigate to the Protect > Backup policies page. Click Create. The Create Policy wizard displays.
  2. Type a name for the policy.
  3. Select DynamoDB from the Add asset types drop down menu.
  4. On the Configure DynamoDB screen, select frequency and retention options. The default selection of backup every 6 hours and retain for 1 day is mandatory for DynamoDB. Edit these settings per your requirements.
  5. On the Additional options panel,
    1. Select a backup destination to store your DynamoDB backups. A SecureVault backup is saved in the same region by default, or you can select a specific region in which to save the backup.
    2. You can choose to enable continuous backup for DynamoDB (this is optional). Continuous backups create incremental backups of your DynamoDB tables, this gives you the ability to restore your tables to any point in time during the retention period.
    3. You can also choose to enable Clumio-managed AWS snapshots. These snapshots are taken by AWS and stored in your AWS account. Select frequency and retention options per your requirements.
      NOTE: If you later make changes to these frequency and retention settings from the AWS management console, these changes will override the selections you made on the Clumio platform.
  6. Review your selections on the Create policy page. Your selections are organized into frequency and retention sets based on the asset types that support those settings. You can add new or edit existing asset types. You can also edit the Additional options you selected.
  7. Click Save to save the policy and have it display on the Backup policies page.

Now that you have created a policy, you can apply it to your DynamoDB tables using protection rules.

Edit a DynamoDB policy

You can edit a policy from the Create policy screen of the wizard before you save it, or later from the Backup policies page.

To edit a policy, click the edit icon.

Delete a DynamoDB policy

Deleting a policy will not affect any backups that have been generated by the policy in the past. Deleted policies cannot be recovered. A policy cannot be deleted if it is protecting workloads. Before you delete a policy, remove it from all of the data sources to which it is applied.

To delete a policy, click the delete icon.