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 environment,  the timeout may be set to a low number, such as 1 minute.

Please check the ELB timeout in your AWS console and increase it to fix the issue. The following is a link to the AWS Steps to adjust the timeout https://aws.amazon.com/blogs/aws/elb-idle-timeout-control/

When an ELB in your environment is causing a timeout, you may see the following in the cpm_server.log file

2020-01-29 22:22:18,242:[140151015565056][YXARihgZcW] ERROR: explore_backup_init(views.py:140) Failed to init explore session

Traceback (most recent call last):

File "./cpmserver/cpm/filemanager/views.py", line 137, in explore_backup_init

File "./cpmserver/cpm/filemanager/mount_volumes.py", line 153, in execute

File "/opt/n2wsoftware/python/lib/python2.7/site-packages/django/db/models/base.py", line 696, in refresh_from_db

db_instance = db_instance_qs.get()

File "/opt/n2wsoftware/python/lib/python2.7/site-packages/django/db/models/query.py", line 380, in get

self.model._meta.object_name

DoesNotExist: FLRWorker matching query does not exist.

If you experience the symptoms mentioned above, please increase the timeout in your ELB and then test FLR after the increase.

• Related Articles

• 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 ...

• 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 ...

• N2WS-20407 - FLR file corruption

  Issue: Due to recent changes in Cloud API's, the following possible issues may occur when using File Level Recovery: 1) Some files/folders may be missing from the view. 2) Some files may be recovered with an incorrect content (unbeknownst to the ...

• CPM installation may fail when the instance is fronted by an Elastic Load Balancer (ELB) or an Application Load Balancer (ALB)

  Background: By default when creating a new AWS Elastic Load Balancer (ELB) or an Application Load Balancer (ALB) it has a default timeout of 60 seconds. During the CPM installation this timeout value can be exceeded and cause the CPM installation to ...

• 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:  ...