Help CenterClumio Terraform ProviderClumio Python SDKClumio GO SDK
BlogChangelogLogin

EBS

Suggest Edits

Clumio offers a secure way to protect your AWS Elastic Block Store (EBS) volumes through SecureVault backup and EBS AWS snapshot policies. Clumio's SecureVault backups represent full, standalone copies of your EBS volumes. Each backup is saved remotely to Clumio and retained for the length of time set by a Clumio policy. During the retention period, you can restore an EBS volume from any unexpired EBS backup. The entire backup volume can be restored to the same account, overwriting the original source volume to roll it back to an earlier point in time, or to a completely different location. After the retention period expires, the backup is destroyed. Clumio offers two tiers of SecureVault backup, Standard and Lite, for more information see, EBS backups and snaps.

EBS AWS snapshots capture instantaneous pictures of your EBS data at a certain point in time. Snapshots are stored within your own AWS account and managed by Clumio. Each snapshot is stored in the same location as the EBS volume–your AWS account–and retained for the length of time set by the Clumio unified policy. During the retention period, you can restore an EBS volume from any unexpired EBS AWS snapshot. Snapshots can only be restored to the same AWS account and saved as a separate volume.

A Clumio policy determines the backup frequencies and retention periods for each EBS volume that it protects. For example, a policy can be configured to back up EBS volumes to SecureVault backup every day and retain each of those backups for 30 days, and the same policy can be configured to generate snapshots every hour and retain each of them for 24 hours.

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

The EBS volumes page is filtered by 'Active volumes' by default and displays the following information:

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

The EBS volumes listed include both supported and unsupported volumes. Unsupported volumes, which appear in gray font with a gray background, are ones that Clumio cannot back up. Clumio cannot back up the following types of volumes:

  • AWS Marketplace AMI root volumes.
  • Volumes that exceed a certain maximum size disk size.

Click an EBS volume ID on the Active EBS volumes page to view its attributes, backup 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.

To view deleted EBS volumes, select the Deleted volumes option from the drop down filter. This lists all of the EBS volumes that have been deleted through the AWS account but still have active SecureVault backups or snapshots. A Clumio process periodically scans the list of deleted EBS volumes to remove volumes that no longer have unexpired/active backups. The process of restoring SecureVault backups or snapshots from a deleted volume is the same as restoring SecureVault backups or snapshots from an active volume.

Updated 3 months ago