Skip to main content
Druva Documentation

Archive EBS Snapshots to Amazon S3 Storage

The availability of this feature may be limited based on the license type, region, and other criteria. To access this feature, contact your Druva Account Manager or Druva Support.

Enterprises often need to retain long-term backups for business continuity, compliance, customer contracts, and e-Discovery. Storage optimization is an ongoing process of evaluating your data storage needs and choosing a cost-effective AWS storage option that meets business needs. However, AWS does not currently offer an out of box low-cost storage tier for EBS snapshots.

You can now transition your Amazon EBS snapshots to Amazon S3 storage classes such as Amazon S3 Glacier and Amazon S3 Glacier Deep Archive, significantly reducing costs while retaining long-term availability.

Key Advantages

Archiving EBS snapshots to S3 offers the following benefits:

  • Cost benefits: Transitioning snapshots to lower-cost storage offers significant savings on long-term retention.
  • Recovery: Seamless recovery of individual files or snapshots from S3.
  • File-level search in snapshots: Metadata-based file search to locate files from the snapshots, without having to recover snapshots in S3.
Note: The Archive Snapshots to S3 feature is currently available only for EC2 snapshots and AMIs.

Manual Archive of EBS Snapshots to S3 

To manually archive your EBS snapshots to Amazon S3 storage:

  1. Login to the Druva CloudRanger console and navigate to Backups.

  2. Select the snapshot that you would like to archive and then click icon.PNG Select Move to S3 from the drop-down menu.

    Arch Bk popupRN.png
  3. Select the appropriate Storage Class to which the backup is to be transitioned.
  4. Click Archive.

    ​​​Once the backup is archived to S3, Druva CloudRanger deletes the original snapshot. However, any policy-based retention remains active.
Note: Selecting an AMI will also move any associated EBS snapshots to S3. Similarly, to move an individual EBS snapshot that has an AMI associated, you will also need to simultaneously select the other associated snapshots.

Archiving an individual snapshot with an AMI association displays the following error:

AMI Snap2.png

For more information about available AWS storage classes, refer to the AWS documentation.

  • Was this article helpful?