Avamar: Não é possível restaurar arquivos do backup da VM usando FLR
Summary: Não é possível restaurar arquivos do backup da VM usando FLR, pois o proxy não é capaz de resolver o nome DNS de destino de backup.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
N/D
- A procura por backups de VM usando FLR falha e exibe a mensagem de erro abaixo:
- Até mesmo a VM que estamos procurando não está atingindo nenhum dos limites de FLR.
- Ao verificar os logs de FLR no proxy, podemos ver as mensagens de erro abaixo no arquivo MountMgr.log, localizado no diretório /usr/local/avamarclient/bin/logs indicando que o proxy não consegue obter a lista de backups do servidor de destino de backup (DD) e que ele não está lá:
[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
- Mesmo no caso de existirem backups e os verificarmos, conforme mostrado abaixo no nó do utilitário do Avamar:
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
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
- Também podemos ver que o IP correto do Avamar já está no arquivo axionfs.cmd localizado no diretório /usr/local/avamar/var, conforme mostrado abaixo:
--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)
--id=restoreonly
--password=#################################
--fuseoptions='-s -r -f -o allow_other,use_ino'
--primarybackupdir=by-number
--inactivity_timeout=172800
--encrypt=tls
--encrypt-strength=high
(END)
Cause
-
O proxy que está sendo usado não é capaz de resolver o FQDN do Data Domain ou o servidor de destino de backup, pois podemos ver o erro abaixo no axionfs_xxxxxxx_xxxx_xxxx_xxxxxxxxxxxx.log mais recente, localizado no diretório /usr/local/avamar/var:
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'
[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'
Resolution
Para resolver esse problema:
- Certifique-se de que o proxy do Avamar seja capaz de resolver o FQDN executando o comando abaixo no proxy:
- nslookup <datadomain_FQDN>
- nslookup <datadomain_IP>
- Se não houver saída válida para datadomain, edite o arquivo /etc/resolve.conf no proxy e adicione o nome DNS correto.
- Adicione o FQDN e o IP para Datadomain ao arquivo /etc/hosts do proxy.
Affected Products
AvamarProducts
Avamar, Avamar Client for VMwareArticle Properties
Article Number: 000067854
Article Type: Solution
Last Modified: 06 Nov 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.