Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell EMC Avamar 19.7 Release Notes

File level restore client known issues

The following table lists the file level restore client known issues in this release:

Table 1. File level restore client known issues
Issue ID Subject/Functional area Description Workaround/Resolution
280373 Issue when browsing a large number of files with Internet Explorer When browsing a folder with large number of files (more than 40,000), Internet Explorer may take more than 2 minutes to complete loading the page, and is not responsive during the loading process. The interim solution to this problem is to use another browser, such as Chrome or FireFox. NA
304444 Files not cleaned up on target device when workorder failure occurs during file level restore on Linux When a workorder failure occurs during a file level restore on Linux due to insufficient space on the target device, the partially copied files do not get cleaned up from the target device, which can result in disk space issues. For example, if restoring 5 GB of files and the target device has only 2 GB of free space, the file level restore fails when the device capacity is reached, but the 2 GB of already copied files remain on the target device. NA
321697 esc 37736 FLR fails when esxi has configured multiple network interfaces but hostname connection unreachable. FLR using esxi hostname failback method fails the whole FLR process even if there is optimal network route. This issue is observed when a proxy connects to ESXi host and hostname connection has an error. FLR fails because it does not support selecting optimal network from route table. NA
332141 If the target Linux virtual machine contains a Btrfs file system with huge file system metadata, FLR operations can either fail or be slow. During an Avamar FLR browse or mount operation, a Linux process to change the file system UUID starts on the Avamar proxy host before the file system is mounted.

With a Linux 4 kernel, the Btrfs UUID change process requires all metadata blocks to be rewritten. This process requires a lot of time, and IO operations. The FLR browse operation works with a "read-only" copy of the backup. The metadata rewrite operation stores the write changes in a temporary file system space on the Avamar proxy host. If the temporary file system space is full or almost full, the FLR operation can fail or be slow.

Perform any of the following workarounds on the Avamar proxy host:
  • Add extra disk space.
  • Change the file system.
  • Stop deduplication and other file system features that result in huge metadata.

Restore operations fail when deselecting a few files from a folder containing 20,000 files

To workaround this issue, complete the following:

  1. Use Apache Tomcat to enable Port 8543 which has an unlimited post size. Port 443 has a post size limit and causes restore operations to fail from folders with 20,000 or more files.
  2. Start the Data Protection Backup and Recovery File-Level Restore UI.
  3. Browse to https://VMware_Backup_Appliance_Host:8543/flr.
  4. Select the files that you are required to restore. Ensure that all the files in the folder are not selected.

Rate this content

Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\