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 for VMware 19.7 User Guide

File Level Restore troubleshooting and limitations

Review the following information related to FLR troubleshooting and limitations:

File Level Restore limitations

Note the following limitations to FLR support:

  • You cannot restore or browse symbolic links.
  • Browsing either a specified directory that is contained within a backup or a restore destination is limited to 50,000 files or folders.
  • Restore is limited to 20,000 objects (files or folders) in the same restore operation.
  • You can restore files from a Windows backup only to a Windows machine, and files from a Linux backup only to a Linux machine.
  • When performing a file-level restore to a /tmp location, the Avamar software redirects data to a private /tmp location.

    For example: /tmp/systemd-private-*

  • To overwrite ACLs of an existing file or folder, ensure that the user has ownership rights of the target file or folder that is being overwritten.
  • On a Linux virtual machine that is configured with the Logical Volume Manager (LVM), an FLR operation in concurrence with a backup operation sometimes fails, and displays the following error message:

    Failed to get the file's properties.

  • fdisk on a proxy displays the GPT partition as Linux file system.
  • /etc/fstab does not contain GPT PARTUUID and PARTLABLE.
  • All virtual machine clients must be in /vCenter/VirtualMachines subfolder in the AUI. Any other location for the VMs is not supported.
  • Only one vCenter is allowed to be configured for the AUI for FLR WEB UI to work.
    NOTE:If more than one vCenter is configured in Avamar, you must ensure that the Avamar server's vcenter-sso-info.cfg reflects the correct vCenter server for the VC_hostname parameter. For example, the sample file /usr/local/avamar/var/ebr/server_data/prefs/vcenter-sso-info.cfg:
    vcenter-sso-hostname=<VC_hostname>
    vcenter-sso-port=7444
    # configure only if more than one vCenter
    vcenter-hostname=<VC_hostname>

Unsupported virtual disk configurations

FLR does not support the following virtual disk configurations:

  • Filesystems that support FLR require a higher kernel than proxy operating system. For example, ext4 sparse_super2, encryption, and project quotas.
  • Encrypted or compressed partitions or bootloaders
  • Deduplicated NTFS
  • Browsing of multiple active disks or partitions. Only the first active disk or partition displays for browsing.
NOTE:FLR operations on virtual machines with Logical Volume Manager (LVM) configurations are supported only if the LVM configuration is complete. A complete LVM configuration consists of at least one partition that is configured with a type 83/8E-Linux LVM, which consists of one or more physical volumes. These physical volumes contain one or more volume groups that are made up of zero or more logical volumes.

RSA 2FA verification errors

If you enabled RSA 2FA for FLR and experience any errors during 2FA verification, these errors likely originate from the RSA server. Contact your RSA administrator for assistance checking the RSA server log and troubleshooting these errors.


Rate this content

Accurate
Useful
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: <>()\