Avamar: Unable to restore files from VM backup using FLR

摘要: Unable to restore files from VM backup using FLR due to proxy not able to resolve the backup target DNS name.

本文适用于 本文不适用于 本文并非针对某种特定的产品。 本文并非包含所有产品版本。
查看其他资源

症状

N/A 

  • While browsing VM backups using FLR, if fails showing below error message:
 
     kA23a000000GJ2pCAG_3_0
  • Even the VM we are browsing is not hitting any of the FLR limits.
  • By checking FLR logs on proxy, we could see below error messages in MountMgr.log file located in /usr/local/avamarclient/bin/logs directory indicating that proxy is not able to get the backups list from backup target server (DD) and that it is not there:
[MM - DEBUG] TID=140213502355139 MID=30870: sAssetPath = /mnt/dunion/<vCenter_name>/VirtualMachines/<VM_name_UUID>/by-number/0000149 [MM - DEBUG] TID=140213502355139 MID=30871: sClientId = [MM - DEBUG] TID=140213502355139 MID=30872: sMountedAvFS = /mnt/dunion/<vCenter_name>/VirtualMachines/<VM_name_UUID>/by-number/0000149/VMFiles [MM - ERROR] TID=140213502355139 MID=30873: HLPR_ListOfDirectories failed for /mnt/dunion/<vCenter_name>/VirtualMachines/<VM_name_UUID>/by-number/0000149/VMFiles [MM - FUNC] TID=140213502355139 MID=30874: IVmdkManager::GetAllAvailableDiskIndexes LEAVE [MM - ERROR] TID=9923 MID=30875: Unable to find backed up VMDK images for: /mnt/dunion/<vCenter_name>/VirtualMachines/<VM_name_UUID>/by-number/0000149
 
  • Even if backups is existing if we checked it as below from Avamar utility node:
mccli backup show --name=/<vCenter_name>/VirtualMachines/<VM_name_UUID>
0,23000,CLI command completed successfully.
Created             LabelNum Size     Retention Hostname                           Location Consistent Level Tier
------------------- -------- -------- --------- ---------------------------------- -------- ---------------- ------
yyyy-mm-dd hh:mm PM 149      ##.# GB D         <AVAMAR_FQDN>                       Local    file             Active

 
  • Also we could see that the correct Avamar ip is already in the axionfs.cmd file located in /usr/local/avamar/var directory as below:
--server=xxx.xxx.xxx.xxx
--id=restoreonly
--password=#################################
--fuseoptions='-s -r -f -o allow_other,use_ino'
--primarybackupdir=by-number
--inactivity_timeout=172800
--encrypt=tls
--encrypt-strength=high
(END)

原因

  • Proxy being used is not able to resolve the Datadomain FQDN or backup target server as we could see below error in the latest axionfs_xxxxxxx_xxxx_xxxx_xxxxxxxxxxxx.log located in /usr/local/avamar/var directory:
     

axionfs Info <10539>: Connecting to Data Domain Server "DD_FQDN"(1) (LSU: avamar-xxxxxxxxxx, User: "ddboost")
[axionfs] netsys::getaddrinfo failed for DD_FQDN: Name or service not known
axionfs Error <10541>: Failed to resolve Data Domain Server name "DD_FQDN" to an IP address. Data Domain login FAILED
axionfs Error <10512>: Problem logging into the DDR server index:1
axionfs Error <11014>: Could not open DDR for /, #146
[axionfs] context::loop: Nothing pending on server, only internal work (pending all=4, ext=0, int=0)
axionfs Warning <19046>: Unable to get ddr_files.xml for clientid <VM_CID> and backupid <backupid>
axionfs Warning <19047>: Unable to retrieve DDR info for 'VMConfiguration'
axionfs Error <41308>: Cannot iterate contents of '': Unable to set location information in direlem_iter for 'VMConfiguration'

解决方案

To resolve this issue:
  • Make sure that AVamar proxy is able to resolve FQDN through running below command on proxy:
  1. nslookup <datadomain_FQDN>
  2. nslookup <datadomain_IP>
  • If there is no valid output  for datadomain  then edit the /etc/resolve.conf  file on proxy and add the correct DNS name. 
       OR 
  • To add FQDN and IP for Datadomain into proxy's /etc/hosts file.

受影响的产品

Avamar

产品

Avamar, Avamar Client for VMware
文章属性
文章编号: 000067854
文章类型: Solution
上次修改时间: 06 11月 2025
版本:  3
从其他戴尔用户那里查找问题的答案
支持服务
检查您的设备是否在支持服务涵盖的范围内。