A c5 instance recovery from snapshot may fail
If
CPM didn't backup a c5 instance with initial ami (snapshots only), the
recovery may fail with the following error:
To
recover a c5 instance you will need to use the AWS CLI to create an AMI to be
used during recovery.
The
examples below are performed in Powershell and the full commands
are one-liners. If you are using other AWS CLI tool or other methods
(JSON file for example), please be aware that syntax may change.
aws ec2
register-image --region us-east-1 --name Mycliimage2 --architecture x86_64 --ena-support
--virtualization-type hvm --root-device-name /dev/xvda --block-device-mappings
'[{\"DeviceName\": \"/dev/xvda\", \"Ebs\": {
\"SnapshotId\": \" snap-00f4223c8ec62fc76\"} }]'
Powershell
will return the value of the image id created like the example below:
{
"ImageId": "ami-c3d9f9b9"
To
recover the instance from the image and attach its volumes from
snapshots use the following command:
aws ec2
run-instances --region us-east-1 --image-id ami-a0dfebda --count 1
--instance-type c5.large --key-name NVirginiaKP --security-group-ids
sg-eaba249e --subnet-id subnet-a18558fb --block-device-mappings
'[{\"DeviceName\": \"/dev/sdb\", \"Ebs\": {
\"SnapshotId\": \"snap-0dd8a4ee636e27d60\"}
},{\"DeviceName\": \"/dev/sdb\", \"Ebs\": {
\"SnapshotId\": \"snap-0dd8a4ee636e27d60\"} }]'
Make
sure you set the correct values to match your desired:
- Region
- Image
- Instance type
- Key name
- Security group
- Subnet
- Block device mapping is properly mapped to additional volume(s) or omitted if you don’t wish to attach additional volumes.
Powershell should return a response with all instance details if command
was successful
Related Articles
Recovery fails with "Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'xxxx.XXXXX' instance type. Ensure that you are using an AMI that is enabled for ENA."
When attempting a windows instance recovery with ENA enabled, it may fail with the following error: "Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'xxxx.XXXXX' instance type. Ensure that you are using an AMI that is ...Error "Could not share private image ami-12345678 between accounts" may occur during cross-account instance recovery
Error "Could not share private image ami-12345678 between accounts" may occur during cross-account instance recovery: Error - Could not share private image ami-12345678 between accounts Error - First step (launching instance) failed. Reason: Could ...Error on Instance recovery - Instance recovery failed: Failed checking snapshot availability
Issue: Error - Instance recovery failed: Failed checking snapshot availability When running a recovery, first CPM downloads the data from the bucket, then it creates a temporary snapshot and then creates the instance. This error occurs when a timeout ...Instance recovery may fail with the error "You are not authorized to perform this operation"
Instance recovery may fail with the error "You are not authorized to perform this operation" : ERROR: recover_ebs_based_instance(.\cpmserver\cpm\recovery.py:749) Run_instance failed. Exception: EC2ResponseError: 403 Forbidden <?xml version="1.0" ...Recovering windows instance might fail with error: The request must contain the parameter ImageID
Issue: When recovering instance from DR account to DR account, it might fail with the following error in logs: 2020-09-22 00:16:35,135:[140237924660992][----------] ERROR: execute_api_call(__init__.py:140) Failed calling ec2.run_instances (region: ...