Error on Instance recovery - Instance recovery failed: Failed checking snapshot availability

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 (one hour – see highlighted in the timestamp below) is reached while CPM is waiting for AWS to complete the temporary snapshot portion of the process. 
 
03-02-24 18:20:17 - Info - Worker i-1234567912345678 successfully launched for account cpm,user (user: admin), region US East (Ohio)
03-02-24 18:43:35 - Info - Volume recovered successfully: vol-12345621598632445 (orig: vol-1265482395247856)
03-02-24 18:43:35 - Info - Creating instance
03-02-24 18:43:38 - Error - Could not kill worker machine i-12345678912345678 in region us-east-2. Error: The instance 'i-136524985632154' may not be terminated. Modify its 'disableApiTermination' instance attribute and try again.
03-02-24 19:44:14 - Error - Instance recovery failed: Failed checking snapshot availability (Recovery of Copy of Policy: Daily, Time: 2024-02-28 02:00:12 , snapshot: snap-02365236985654125)

Solution 1: You can increase the default timeout parameter - the default is 1 hour (3600 sec).
You can increase this value from the default 3600 sec (1 hour) to 7200 sec (2 hours).
 
Steps:
1. SSH into the CPM server
2. Create or edit the following file:
/cpmdata/conf/cpmserver.cfg​
3. add the below parameter
[backup_copy] 
create_restored_volume_snapshot_timeout_in_seconds=7200
4. When no backups are running, restart the Apache server
sudo service apache2 restart
 
Solution 2:
You can launch the recovery again with different options. This time within the basic recovery options, in the "Launch from" field, select the option “Image (replace root volume)”  this should allow the recovery and avoid the timeout issue.