4. Performing a Basic Recovery

N2WS backs up the requested objects at the requested times. When you return to the main console after a while, you can view the backups in the Backup Monitor tab:

Figure 4‑1

For each backup, you can see exact start and finish times, and status. Click View in the Snapshots column and see the individual EBS snapshots of all the volumes. Click Open in the Log column to view the log of this backup with all the details. In order to recover from a particular backup (typically the most recent successful backup), click the Recover button in the Actions column:

Figure 4‑2

In the Recovery Panel screen (Figure 4‑3), you can see all the instances that this backup contains. Should this policy include also EBS volumes, RDS databases, Redshift Clusters or DynamoDB Tables, you will have a link to recover them as well. In order to recover an instance, click the Instance button. The Volumes Only button is for recovering only the EBS volumes of the instance without actually creating a new instance.

You will now see the Instance Recovery page:

Click Advanced Options for additional recovery parameters.

Figure 4‑3

Most of the options when launching EC2 instances are available here and may be modified. The currently selected defaults are exactly the options the original backed-up instance had at the time of the backup, including the tags associated with it. Clicking the Recover Instance button will recover an instance exactly like the original one.

Important: If you intend to test the recovery of an instance in the same region as the originally backed up instance, you will need to change the IP in order to avoid an IP conflict. This can be mitigated by leaving the VPC Assign IP box blank:

A further option worth mentioning here is Launch from. This sets the option for the image the new instance will be launched from. In case of an instance-store-based instance, the only option would be to launch from an image. The default will be the original image, although it can be changed. In case it is a Linux EBS-based instance, as in this example, and the backup includes the snapshot of the boot device, you can choose between launching from an image (the original image or another), and launching from the snapshot, which is the default. If you choose to launch from a snapshot, a new image (AMI) will be created, and you can choose whether you want to keep the image after the recovery is complete or deregister it. You can even choose not to perform the recovery now, and only create the image, to recover from it later.

If Capture VPC Environments was enabled in General Settings, the Advanced Options section will also contain a Clone Original VPC option next to the VPC box.

The Clone Original VPC option allows you to recover the instance to a clone of a selected VPC environment. See the N2WS Backup & Recover (CPM) User Guide for details on “Recovering to a Cloned Original VPC”.

After you click Recover Instance and confirm, you will be directed back to the recovery panel page, and will get a message about the operation success:

Figure 4‑4

The message will include the instance ID of the new instance, and now you can go and verify the successful recovery in the AWS Management Console. The recovered instance is exactly the same as the original one, with all its EBS volumes.


Share this post →

Share on twitter
Share on linkedin
Share on facebook
Share on email
Fast-growing organizations around the world use N2WS
client logo - news UK
client logo - coca cola
client logo - nasa
client logo - atos
client logo - cisco
client logo - deloitte
client logo general dynamics
client logo - philips