> This page is for Data Protection. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.eon.io/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.eon.io/_mcp/server. # EC2: Restore a Volume This article explains how to restore an EBS volume from your Eon snapshots using the standard restore method. Standard restore fully restores the volume from your vault before it becomes available. For faster recovery where the volume becomes available in minutes while data loads in the background, see [EC2: Restore a Volume (Instant Restore)]. [EC2: Restore a Volume (Instant Restore)]: /data-protection/restoring/restore-cloud-workloads/aws/ec2/ec2-restore-a-volume-instant-restore The process for restoring an EBS volume can be divided into two main parts: * [Part 1: Restore the volume](#part-1-restore-the-volume) takes place in the Eon console, where you'll choose the snapshot to restore, set the restore details, and start the restore job. Depending on the size of the volume you're restoring, you might need to wait a bit before moving on to part 2. * [Part 2: Mount the restored volume to an EC2 instance](#part-2-mount-the-restored-volume-to-an-ec2-instance) takes place in the AWS Management Console, where you'll attach the restored volume to an EC2 instance. ## Decide whether to convert to an EBS snapshot or restore A volume can be converted to an EBS snapshot or restored as an EBS volume, so you'll need to decide which option is best for your case: | EBS snapshot | Volume restore | | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | | * Can be shared with another availability zone or region. * Can be used to create multiple copies of the volume. | - Deployed in a specific availability zone. - Can be attached only to instances in the same zone. | This article covers restoring a volume. If you want to convert the Eon snapshot to an EBS snapshot, see [EC2: Convert a Volume to EBS Snapshot]. [EC2: Convert a Volume to EBS Snapshot]: /data-protection/restoring/restore-cloud-workloads/aws/ec2/ec2-convert-a-volume-to-ebs-snapshot ## Part 1: Restore the volume #### Before you start Before you restore a volume, make sure: #### Find the snapshot you want to restore 1. In your inventory , select the EC2 resource you want to restore. The **Resource Details** drawer opens. 2. Click the **Eon snapshots** tab. You'll see a calendar view with colored dots on the days when snapshots were taken. There can be more than one snapshot per day. When you click a day, a list of Eon snapshots taken that day is displayed below the calendar. 3. Expand the snapshot you want to restore. Click **Specific volume**, select the volume you want to restore, and then click **Restore**. The **Restore Volume** wizard opens. #### Choose the restore account and method In the **Restore Volume** wizard, the first step is to choose a restore account and method. 1. Choose the cloud account you want to restore the volume in. 2. Make sure **Use instant restore** is off. 3. Click **Next**. #### Set the restored volume details In the **Configuration** step, you'll set the restored volume details. 1. Choose a **Region** and **Availability zone** to deploy the restored volume to. 2. Choose whether to turn **Keep original settings** on or off. * If you leave **Keep original settings** on, the restored volume retains the same settings as the original volume. * If you turn it off, you can customize the volume's **Type**, **Size**, and **IOPS**. 3. In **Encrypt this resource**, select a KMS key that grants access to `EonRestoreAccountRole` and `EonRestoreNodeRole`. You can either select a key from the **Encryption key** list or enter a **Key ARN**. 4. If you want to retain the tags that were present when the snapshot was taken, turn **Keep original tags** on. Otherwise, turn **Keep original tags** off. In both cases, the new volume is tagged with `eon:restore=true`. Tags with the `eon:` prefix aren't included in the original tags because Eon uses this prefix for internal operations. #### Start the restore job Click **Start** to start the asynchronous restore job. You can see your list of restore jobs on the Restore jobs tab in the Jobs page. When the job completes, the status changes to **SUCCESS**, and you can work with the restored volume as normal. You can continue to part 2, where you'll attach the volume to an EC2 instance. ## Part 2: Mount the restored volume to an EC2 instance #### Before you start Before continuing, make sure the restore job in part 1 has a status of **SUCCESS**. #### Attach the volume to an EC2 instance 1. Find or create an EC2 instance in the same availability zone where you restored the volume, and [attach the volume to it][aws-attach-volume]. 2. Connect to the EC2 instance and run this command to confirm the volume was attached: ```sh lsblk ``` Your new volume doesn't have any mount points yet. 3. Remember the new volume's name, which you'll need in the next step. The name listed in the `lsblk` output might not match the name you assigned when you attached the volume. #### Mount the volume 1. Create a directory where you want to mount the volume. ```sh sudo mkdir /data ``` For these instructions, we'll use `/data`, but you can use any name you want. 2. Mount the volume to the directory you created. Replace `$VOLUME_NAME` with the name of the volume you found in the `lsblk` output. ```sh sudo mount /dev/$VOLUME_NAME /data ``` 3. Confirm the volume is mounted: ```sh df -h ``` > **Tip** > > If you want the volume to mount to the instance on every boot, see [Making an Amazon EBS volume available for use](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-using-volumes.html) from AWS. [aws-attach-volume]: https://docs.aws.amazon.com/ebs/latest/userguide/ebs-attaching-volume.html