This section explains how you can restore an individual file from a snapshot, with the file-level recovery functionality.
With the file-level recovery option, you can initiate a recovery instance and choose the files you want to recover This launches an instance in your environment, attaches your volume and hosts it as a web server. The files on this instance will be accessible only on your IP. Files restored on this instance will only be accessible through your IP.
Restoring EBS Snapshots with File Level Recovery
To initiate a file-level recovery:
- Log into your Druva CloudRanger console and navigate to Backups.
The Restore Snapshot page displays an overview of the snapshot with the associated tags.
The File Level Recovery option is selected by default.
How long do you want your instance to be available?
The duration in minutes for which you want the temporary instance to be available to restore the files.
You can specify the duration, but we recommend at least 30 minutes.
Select this option to ensure a faster restore process using an m4.large instance.
Note: Selecting this option will incur additional costs associated with the selected resource.
The 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.
Subnet of the VPC where you want the restored EC2 instance to run.
The restored snapshots are connected to a temporary instance and can be accessed using the link available on the Restores page. The restored instance opens in a new window. It may take up to a minute for the temporary instance to be available, so you may need to refresh the page.
Once the instance becomes available, locate the archived files for downloading. You may also download a directory with one click using the download icons on the right, which will download the archive with a .zip extension.
For more information on EBS snapshots, please refer to the AWS documentation.