Documentation Index

Fetch the complete documentation index at: https://docs.lucidity.cloud/llms.txt

Use this file to discover all available pages before exploring further.

AWS Backup & Restore

  • Updated on May 11, 2026
  • Published on May 11, 2026
  • 2 minute(s) read
Prev Next

Backup & Restore using AWS Backup

Lucidity guarantees that the customer's existing backup and restore process will remain unchanged.

AWS Backup enables you to centralize and automate data protection across AWS services. With AWS Backup, you can create backup policies called backup plans. You can use these plans to define your backup requirements, such as how frequently to back up your data and how long to retain those backups. AWS Backup lets you apply backup plans to your AWS resources by simply tagging them. AWS Backup then automatically backs up your AWS resources according to the backup plan that you defined.

By default, AWS Backup creates crash-consistent backups of Amazon EBS volumes that are attached to an Amazon EC2 instance. Crash consistency means that the snapshots for every Amazon EBS volume attached to the same Amazon EC2 instance are taken at the exact same moment. You no longer have to stop your instances or coordinate between multiple Amazon EBS volumes to ensure crash-consistency of your application state.

📦 Amazon EBS and AWS Backup - AWS Backup

  1. Lucidity_Demo_Instance is onboarded to Lucidity platform and the EBS volumes managed by Lucidity are highlighted in the picture below. All the tags which were part of the existing disk will be replicated to the resulting Lucidity managed EBS volumes

AWS console screenshot showing the Instances list on the left (with Lucidity_Demo_Instance highlighted) and the Volumes list on the right with multiple EBS volumes outlined in a red box; captioned Figure 1 - Lucidity Managed Volumes.

2. The EBS volumes are assigned a tag value of env = backup

AWS console Tags panel screenshot showing a tag row with Key env and Value backup, the tag row highlighted with a red box; captioned Figure 2 - Tag assignment.

3. AWS Backup plan is created with the assigned tag. Backup service creates a backup of all the volumes which has the tag value of env = backup

[IMAGE PLACEHOLDER: Screenshot illustrating backup-protected EBS volumes in the AWS console, showing volumes marked as protected/attached and labeled to indicate backup protection; captioned "Figure 3 - Backup protected EBS volumes".]

AWS Backup console Protected resources view — a table listing EBS volumes with columns such as Resource name, Resource ID (e.g., volume/vol-0c...), Resource type (EBS), and Last backup dates/times.

4. AWS Backup creates a snapshot of all EBS volumes under protected resources as shown below.

AWS Backup console Snapshots view — table of snapshots with Snapshot ID links (e.g., snap-0ec0bd6aa53f82a3), Volume size (e.g., 1 GiB, 2 GiB, 6 GiB), Description text This snapshot is created by the AWS Backup service., Storage tier (Standard), and Snapshot status (Completed).

Figure 4 - Snapshots created by AWS Backup service

5. Recovery points are created by AWS Backup for restoration of the EBS volumes.

Figure 5 - AWS Backup recovery points

AWS Backup console Recovery points view — table showing Resource ID (volume/vol-0c2a058d5832cb4b8, volume/vol-02097660b3453b239, etc.), Resource type (EBS), Backup type (Snapshot), Creation time (e.g., July 14, 2023, 19:30:00 (UTC+05:30)), Source account ID, and Retention period (e.g., 1 day).

AWS Backup console - Recovery points table showing multiple snapshot recovery point IDs in a list, each with a green Completed status icon; includes a filter/search box above and action controls in the top-right.

6. Restore the protected resources using the snapshot recovery point

AWS Backup console - Restore jobs view with the left navigation pane (My account, External resources, My organization) and the main panel showing a table of restore job IDs, status Completed, resource IDs, resource types, and creation time; search/filter box and toolbar visible above the table.

Figure 6 - Restored EBS volumes

7. Attach the restored volumes on a recovery instance.

EC2 Instances and Block devices view - left pane showing an instance list with Lucidity-restore selected; right pane showing a Block devices table listing Volume IDs, device names, Volume size (GiB), and Attachment state with multiple rows highlighted in a red outline and Attachment state Attached.

8. Create a mountpoint and mount the volumes using the below commands

$ sudo mkdir /data_vol
$ sudo mount -o nodatacow,noatime /dev/xvdq /data_vol

Note - The subvolumes of the BTRFS files system share the same UUID which makes it easier to re-mount the multiple volumes as a single mount point. You can choose to mount any one of the devices (/dev/xvdq, /dev/xvdp, /dev/xvdo, /dev/xvdn, /dev/xvdm, /dev/xvdl, /dev/xvdk, /dev/xvdj) present in the BTRFS volume pool.

Terminal screenshot showing sudo blkid output with multiple /dev/xvd* entries, LABEL and UUID fields on a black terminal background; several lines are enclosed in a red rectangular highlight.

9. Run df -hT to verify the mount point.

Terminal screenshot showing commands 'sudo mkdir /data_vol' and 'sudo mount -o nodatacow,noatime /dev/xvdf /data_vol' followed by the output of 'df -hT'; the output table lists filesystems and shows a highlighted line '/dev/xvdm btrfs 26G 1.2M 26G 1% /data_vol'.

Related articles