Help CenterClumio Terraform ProviderClumio Python SDKClumio GO SDK
BlogChangelogLogin

EC2

Suggest Edits

Clumio offers a secure way to protect your Amazon Elastic Compute Cloud (EC2) instances through SecureVault Backup and Snap policies.

SecureVault Backups represent full, standalone copies of your EC2 instances. An EC2 backup protects the following assets of an EC2 instance:

  • EBS storage volumes that are attached to the instance.
  • Root volumes of EC2 instances, including ones that are launched from AWS Marketplace Amazon Machine Images (AMIs).
  • The EC2 instance configuration, including the EBS volumes specification, the paid AWS Marketplace AMIs, and the snapshot configurations. If the instance only contains instance store volumes, Clumio backs up the instance store configuration, but not the instance store volumes. If the instance contains a mix of EBS and instance store volumes, Clumio backs up the EBS volumes only.

Each backup is saved remotely to Clumio and retained for the length of time set by the Clumio unified policy. During the retention period, you can restore the EC2 instance or its individual files and folders from any unexpired backup. After the retention period expires, the backup is destroyed. Clumio offers two tiers of SecureVault Backup, SecureVault Standard and SecureVault Lite, for more information, see EC2 backups.

Snapshots capture instantaneous pictures of your EC2 data at a certain point in time. An EC2 Snap protects the following assets:

  • EBS storage volumes that are attached to the instance.
  • Root volumes of EC2 instances, including ones that are launched from AWS Marketplace Amazon Machine Images (AMIs).

Each Snap is stored in the same location as the EC2 instance - that is, your AWS account – and retained for the length of time set by the Clumio unified policy. During the retention period, you can restore the EC2 instance from any unexpired EC2 Snap. After the retention period expires, the Snap is destroyed.

EC2 backups and Snaps are generated at certain frequencies and retained for a certain amount of time based on the unified policy that protects it. The policy determines the backup and Snap frequencies and retention periods for each EC2 instance that it protects. For example, a unified policy can be configured to back up EC2 instances every day and retain each of those backups for 30 days, and the same policy can be configured to generate Snaps every hour and retain each of those Snaps for 24 hours.

The unified policy also determines whether users are allowed to take backups and Snaps on demand.

The Active EC2 Instances window (AWS > Environments > [Account Name] > EC2 Instances) lists all of the EC2 instances discovered in the AWS account, irrespective of whether the instances are protected or not by Clumio.

The Active EC2 Instances window displays the following information:

  • Instance ID: The AWS-assigned ID of the EC2 instance.
  • Instance name: The name which comes from the value of AWS tag key Name.
  • Tags: The AWS tag key and value assigned to the instance. An instance can be assigned multiple tags.
  • Policy: The Clumio policy that is currently protecting the instance.
  • 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.

From the Active EC2 Instances window, click an EC2 instance ID to view its attributes, backup and Snap history, restored files, and active alerts.

The Protection History calendar displays the dates with available backups and Snaps. A blue dot represents a backup, while an orange dot represents a Snap.

The Deleted EC2 Instances window (AWS > Environments > [Account Name] > Active EC2 Instances > Deleted EC2 Instances) lists all of the EC2 instances that have been deleted through the AWS account but still have active backups or Snaps. A Clumio process periodically scans the list of deleted EC2 instances to remove the ones that no longer have unexpired/active backups. The process of restoring a backup or Snap from a deleted instance is the same as restoring a backup or Snap from an active instance.

Updated 20 days ago