Skip to main content
All CollectionsAWS WorkloadsProtect EBS Resources
Restore Archived Snapshots to an Instance
Restore Archived Snapshots to an Instance
Updated over a week ago

Provides information on restoring archived snapshots to an instance, with options to restore across Accounts or Regions.

Druva CloudRanger allows you to restore snapshots archived to S3 storage to an instance, with options to restore backups across Accounts or Regions.

Before you begin

Before you can restore archived snapshots to an instance, you will need to update your AWS Access Role by deploying the latest CloudFormation template for each account in which you intend to restore snapshots. Navigate to Account Settings > AWS Access, and update your AWS CloudFormation stack/stackset.

Known Limitations to Restoring Snapshots on Windows

A potential limitation when restoring archived snapshots originating from a Windows environment is the MBR/UEFI-based boot partition, which defaults to a Linux boot partition. The restore job proceeds to the final step, where the boot attempt fails, although the data is restored to snapshots and available in AWS.

Perform the steps outlined below once the restore is complete (when the boot attempt fails):

  1. Gather the Snapshot IDs that have been restored from S3, and the blockdevice mapping on the backup (for example, snap-xxx corresponding to mapping /dev/sda1 ).

  2. From each snapshot that was restored from S3, create a volume.

  3. Use the Image ID of the original instance to launch a new instance.

  4. You may customize your instance settings as needed.

  5. Once the instance is in a running state, stop the instance.

  6. When the instance is in the stopped state, detach each volume, and reattach the volume created from the snapshots restored.

  7. Start the instance, and once running, you may use the password for the original instance to access the data.

Restoring Archived Snapshots as an Instance

To restore an archived snapshot to an instance:

  1. Log into your Druva CloudRanger console and navigate to Resources > EBS.


  2. Navigate to the Backups tab and apply the S3 Archive filter to view archived snapshots.
    By default, Snapshots and S3 Archive are displayed under EBS Backups.

    2_Restore S3.png

  3. Select the archived snapshot that you wish to restore, and then click Restore.

    β€‹πŸ“ Note
    ​Temporary resources will be required to restore snapshots from S3 Archives, and CloudRanger will trigger a notification before initiating the restore.


  4. Click Proceed.
    The Restore Snapshot page displays an overview of the snapshot with the associated tags.

  5. Select the Restore as an instance option.

    πŸ“ Note
    ​When restoring a snapshot from S3 Archive, the File level recovery option will remain disabled. This feature will be supported as part of upcoming enhancements.


  6. ​You can choose to modify the following settings, as applicable and then click Confirm.





By default, Druva CloudRanger displays the name of the original EC2 instance, and if unavailable, the instance ID is used as the name.
You can choose to modify the default instance name.


Select the processor architecture for the instance, for example, i386.

Instance Type

Select an instance type of the restored EC2 instance. By default, Druva CloudRanger selects the original EC2 instance type.

πŸ“ Note

Not all instance types are supported in all regions. If you run into issues with the restore, verify that the selected instances are supported for that region.

For more information, refer to the AWS documentation.

Image ID

The ID of the associated AMI.



This section displays the tag keys that have been specified for the source EC2 instance or the AMI.
Tags act as metadata to help identify and organize your AWS resources.


The Value will depend on the Key specified.
​Key: Created by Policy ; Value: New



Select the Druva CloudRanger Account to which the archived snapshot is to be restored.


Select the AWS Region to which the archived snapshot is to be restored.

πŸ“ Note
​Druva CloudRanger now supports cross-account and cross-region restores when restoring snapshots as an instance.


A virtual private cloud (VPC) where you want the restored EC2 instance to run.


Subnet of the VPC where you want the restored EC2 instance to run.


Virtualization type for the restored EC2 instance.


Key Name

The backup encryption target key for the EC2 instance.
If you plan on remotely connecting to the restored EC2 instance, select a key pair created in your account.

Instance Profile

Instance profile for the restored EC2 instance.

Security Groups

Security group for the restored EC2 instance.

Block Device Mappings

The Device Name, Snapshot ID, Account and AWS Region to which the instance is to be restored.
Click Add to add or delete new devices and snapshot IDs or use the Clipboard icon to remove a device mapping.

The restored snapshots will now be available on the Restores page.

Did this answer your question?