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 (i-0123456789abcdef) to figure out block devices. Reason: AWS was not able to validate the provided access credentials

This can happen if:

1) The access and secret keys you are using for file-level restore belong to an account that doesn't have access to the CPM instance

2) The keys were deleted in EC2.

3) The keys were entered incorrectly or have illegal characters in them - e.g. space at the end of the string

To resolve this issue, please provide the correct/new keys (in "AWS Account for File Level Recovery" under "General Settings").

• Related Articles

• File level restore may fail with the "Failed adding share permission" error

  File level restore may fail with the "Failed adding share permission" error: ERROR:  share_snapshot(.\cpmserver\cpm\aws_utils.py:265)  Failed adding share permission to snapshot snap-1234567890abcdef (original volume: vol-abcdef1234567890) Failed. ...

• File-level recovery may fail with "Reason: In order to use this AWS Marketplace product you need to accept terms and subscribe"

  File-level recovery may fail with the following error printed in the CPM logs: ERROR:  explore_backup_init(.\cpmserver\cpm\filemanager\views.py:368)  File Level Recovery - failed exploring snapshot snap-0123456789abcdef. Reason: Volume ...

• File Level Recovery may fail with error "The reason could be missing/unsupported file system"

  File-level recovery may fail with the following error printed in the CPM logs: Partition Table: gpt Number  Start     End        Size        File system  Name     Flags 1         2097kB   805GB  805GB                          primary    raid INFO:  ...

• File Level Recovery may fail if Elastic Load Balancing (ELB) is in use

  Using FLR to explore volumes may fail if Elastic Load Balancing (ELB) is in use When using FLR to explore files you may get one of the following errors when the worker launches. This could be caused by an ELB (Elastic Load Balancing) in your ...

• Troubleshooting File Level Recovery (FLR) communication issue

  CPM Configuration File-level recovery requires N2WS to recover volumes in the background and attach them to a temporary EC2 ‘worker’ launched for the operation, The worker will be launched in the same account and region as the snapshots being ...