User Data may be restored incorrectly during instance recovery
Issue:
When using an executable script in “User Data” during an instance recovery, the
script does not appear on the restored instance as intended.
Example:
Before instance restore:
After
instance restore:
Fix:
If
you face this issue, please upgrade to latest 2.X.X version
Reference
defect number – N2WS-1349, fixed in v2.4.0
Link to Release Notes and the latest patch
https://support.n2ws.com/portal/kb/articles/release-notes-for-the-latest-v2-4-x-cpm-releaseRelated Articles
Instance recovery may fail with the "Address xxx.xx.xx.xx is in use" error
When attempting instance recovery, it may fail with the following error in the recovery log: Error - First step (launching instance) failed. Reason: Address xxx.xx.xx.xx is in use. This usually happens because you are trying to restore an existing ...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 ...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" ...Instance restore may be marked "successful", despite failing to restore a volume
Issue: A cross account restore of an encrypted volume or instance may be marked successful, however a Volume has failed to restore. Fix: If you face this issue, please upgrade to latest 2.X.X version Reference defect number – N2WS-1168, fixed in ...File-level restore may fail with the "Could not get CPM instance info" error
File-level restore may fail with the "Could not get CPM instance info" error: The following error is printed in the CPM server log: ERROR: explore_backup_init(.\cpmserver\cpm\filemanager\views.py:317) Could not get CPM instance info ...