Clumio unifies in-account automated snapshots and air-gapped backups of your Relational Database Service (RDS) data using a single policy. In this document, RDS resources refer to both RDS instances and Aurora clusters.

For more information about Clumio for RDS, see Getting started with Clumio for RDS.

Clumio offers the following RDS backup tiers to store your RDS backups:

  • SecureVault Standard tier
  • SecureVault Archive tier
  • AWS automated backups

See RDS backups for details.

The Available Resources window (AWS > Accounts > RDS Resources) lists all of the RDS instances and clusters deployed in your AWS account.

The Available Resources table displays the following information:

  • Database Name—Represents the name of an RDS instance or Aurora cluster.
  • Engine—The Amazon RDS database engine type. Examples of supported RDS engines include PostgreSQL, MySQL, and MariaDB.
  • Tags—The AWS tag key and value assigned to the resource (there may be multiple tags). Tags are set through the AWS Management Console.
  • Policy—The Clumio policy that is currently protecting the resources. If the database is protected by a policy, you can edit the policy b clicking the edit icon. You can also add a policy to protect the database from this column.
  • Compliance Status—The compliance status. The state transitions are different for RDS instances that have air-gapped backups and those that have both air-gapped and Granular Record Retrieval (GRR) backups. See RDS backups for more information. The state transitions for an RDS instance that only has air-gap are as follows:
    • In compliance: The asset is compliant with its protection policy; all recurring backups and snap-shots 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 backups 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.
      The state transitions for an RDS instance that has both Air-gap and GRR are as follows (air-gap and GRR are interchangeable in the following):
  • Last Backup—The details about 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 database to view its backup details, including protection history, record retrieval history, alert details, recovery options, and retrieval options.