Possible Reasons for Instance Store-Backed Instance Not Recovered on Replacement Dedicated Host
Question
A start-up firm is using a Dedicated Host for the deployment of Oracle-based applications.
Some of the instances on this Dedicated Host are using instance stored volume, while some are using EBS volumes.
Host recovery is enabled on this Dedicated host.
Due to hardware issues on a dedicated host, a replacement instance was launched.
But you found that instance store-backed instances are not recovered to that host.
What can be possible reasons for the Instance store-backed instance not recovered on replacement Dedicated host?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer - B.
Instance store-backed instances are not automatically recovered on replacement Dedicated host post Host recovery.
For these instances, a manual approach needs to be followed based upon remedial steps.
Option A is incorrect as No need to open AWS Ticket, Instance store-backed instances can be recovered using remedial steps to a replacement dedicated host.
Option C is incorrect.
Although this will work, this is not required to be recovered to a replacement Dedicated host.
Option D is incorrect as Stopping the instance will not result in the recovery of impaired Dedicated Host.
For more information on Amazon EC2 host recovery, refer to the following URL-
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-recovery.htmlThe reason why the instance store-backed instances are not recovered on the replacement Dedicated host could be due to the following:
Instance store-backed instances do not support automatic recovery: When a Dedicated host fails, Amazon EC2 automatically recovers the instances on the host to a new host. However, instance store-backed instances do not support automatic recovery. Therefore, when a Dedicated host fails, the instance store-backed instances need to be manually recovered.
Configuration of the instance store-backed instance: The instance store-backed instance may have been configured to run on a specific Dedicated host. When the Dedicated host fails, the instance cannot be recovered automatically on a new host. This is because the instance store-backed instance is tightly coupled to the physical host hardware.
Instance store-backed instances need to be re-hosted to EBS-backed volumes: Instance store-backed instances are ephemeral, which means that data stored on the instance store volumes is lost when the instance is stopped or terminated. To avoid data loss, instance store-backed instances need to be re-hosted to EBS-backed volumes.
Therefore, the correct answer to this question is B. Need to perform manual recovery of instance store-backed instances on Dedicated Host following remedial steps. This means that the instance store-backed instances need to be manually recovered by following remedial steps. This includes creating a new instance, attaching the instance store volumes to the new instance, and configuring the instance to use the volumes.
