Avamar: VMware File Level Restore - FLR - Fails: “The VMDK Filename Is Not Valid or Present”
Summary: The following error is displayed when attempting to run Avamar VMware File Level Restore (FLR): "The VMDK filename is not valid or present. Verify that the proxy was correctly registered using the supported method in the documentation." ...
Symptoms
Attempting FLR on Avamar with Data Domain, the following error appears:
"The VMDK filename is not valid or present. Verify that the proxy was correctly registered using the supported method in the documentation."
The /usr/local/avamar/var/axionfs<uuuid>.log file from the proxy used for the backup shows an error similar to this:
axionfs Info <10539>: Connecting to Data Domain Server "dd01.example.com."(2) (LSU: avamar-1399865928, User:"DDBOOST") axionfs Warning <18125>: Calling DDR_OPEN returned result code:5341 message:SSL library error axionfs Error <10542>: Data Domain server "dd01.example.com" open failed DDR result code: 5341, desc: SSL library error axionfs Error <10512>: Problem logging into the DDR server index:2 axionfs Error <11014>: Could not open DDR for /, #397 axionfs Warning <19046>: Unable to get ddr_files.xml for clientid <cid> and backupid 131129312174737330 axionfs Warning <19047>: Unable to retrieve DDR info for 'VMConfiguration' axionfs Error <0000>: Cannot iterate contents of '': Unable to set location information in direlem_iter for 'VMConfiguration'
The /usr/local/avamarclient/bin/MountPoint/MountMgr.log file shows a similar error type:
Unable to find backed up VMDK images for: /mnt/dunion/vc.example/com/VirtualMachines/VM_UBNsDNRK5H3GJv7yiD7ynQ/by-number/0000001
Cause
The FLR process can connect to Avamar to retrieve metadata but is not able to connect to the Data Domain due to an SSL issue.
This issue is described in. Avamar backups or restores to or from the Data Domain fails or completes with exceptions with error messages mentioning "5341" and "SSL library error"
Resolution
In the proxy used for the FLR, add the following flags in axionfs.cmd file under the path /usr/local/avamar/var/:
--ddr-auth-enabled=false --ddr-encrypt-strength=none --ddr-auth-mode=3
You may alternatively add the following option to the restore options:
[avtar]ddr-auth-enabled=false [avtar]ddr-encrypt-strength=none
To do so using Avamar user interface, follow these steps:
Select the More Options button at the bottom right on the restore window Select the More button near the bottom right. Put this in Enter Attribute - [avtar]ddr-auth-enabled Put this in Under Enter Attribute Value: false Click the + button Put this in Enter Attribute - [avtar]ddr-encrypt-strength Put this in Under Enter Attribute Value: none Click the + button Click OK, Then OK again.
Additional Information
A similar resolution can be found in Avamar backups or restores to or from the Data Domain fails or completes with exceptions with error messages mentioning "5341" and "SSL library error"