Snapshots are incremental backups, which means that only the data blocks that have changed since your most recent snapshot will be backed-up. Upon restoring a snapshot, the entire point in time copy is restored. When you delete a snapshot, only the data exclusive to that snapshot is eliminated.
You can choose one of the following approaches to restore an EBS snapshot:
- Restore as an instance
- Restore to a volume
- Request a file-level restore
Restoring EBS Snapshots as an Instance
Druva CloudRanger boots up an EC2 instance using predefined parameters and then attaches the snapshots to be restored as a volume to that instance.
To restore a snapshot as an instance:
- Log into your Druva CloudRanger console and navigate to Backups.
- Select the EBS snapshot that you wish to restore, and then click Restore.
The Restore Snapshot page displays an overview of the snapshot with the associated tags.
The File level recovery option is selected by default.
- Select the Restore as an Instance option to launch an instance from the snapshot.
Restore Instance Using
The restore settings to be used.
- Select Last Synced Instance Settings to use the configuration defined previously.
- Choose Selected Snapshot Settings to launch the restore based on the current settings.
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.
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.
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
Key: Origin; Value: Origin ID
- Click Show Advanced.
You can choose to modify the following settings, as applicable:
The AWS Region where the backed-up snapshot is stored.
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.
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 for the restored EC2 instance.
Security group for the restored EC2 instance.
Block Device Mappings
The Device Name and ID of the snapshot to be restored.
Use the and icons to delete or add new devices and snapshot IDs to be restored.
- Click Confirm.
Druva CloudRanger launches an Instance from this snapshot using the snapshot settings specified, and the initiates the restore. The restored snapshots will now be available on the Restores page.