Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Cannot log in to the vSphere Data Protection Restore Client. The vSphere Data Protection Restore Client returns these errors:Login failed. Cannot locate login client (VM_IP_address) in VDP. Login failed. Cannot locate vm in vCenter In the /space/avamar/var/flr/server_logs/flr-server.log file, you see entries similar to:INFO [http-nio-8543-exec-7]-vi.VIAccess: Attempting to obtain AVE VM with IP Address: [172.16.2.159] INFO [http-nio-8543-exec-7]-vi.VIAccess: Local Client not found WARN [http-nio-8543-exec-7 security.CustomSecurityService: FLR login attempt failed with error code: [cannot.locate.in.vcenter] com.emc.flr.exceptions.LoginException: CANNOT_LOCATE_VDP_LOGIN_CLIENT xx:xx:xx:xx Where the IP address of xx:xx:xx:xx belongs to a machine that is not protected by the VDP appliance.
This issue can occur in these situations: If virtual machine from which the vSphere Data Protection Restore Client was launched has never been added to a backup job on the VDP appliance used in the URL to access the Restore Client. If the network appliance is using network address translation (NAT) and is sending all VDP traffic through a proxy/firewall. If the user did not install VMware Tools in the virtual machine trying to access the portal. If using Windows Server running vCenter with Microsoft SQL Server 2008 RTM (Version 10.0.1600.22(x64)).There is a known issue when a complex query is run that contains aggregate functions, join functions and distinct functions in sub queries. This may cause the File Level Restore (FLR) to return incorrect results and display the error:Login failed. Cannot locate login client (VM_IP_address) in VDP. If there are multiple virtual machines with the same IP address in the vCenter Server inventory.
To resolve this issue, log in to a virtual machine where a backup job has been created and run to allow for file level restores. If the issue is due to a firewall/proxy, exclude all VDP traffic from using this route. If the issue is due to missing VMware Tools, another backup with the VMware Tools is not required. Simply installing VMware Tools in the virtual machine corrects the authentication error. For more information, see the VMware vSphere Data Protection Documentation. Pay particular attention to the section starting on page 143. If the issue is due to Microsoft SQL version, upgrading to Microsoft SQL Server 2008 R2 SP2 should resolve the issue. For more information, see List of the bugs that are fixed in SQL Server 2008 R2 Service Pack 2. Note: The virtual machine needs to be on the same vCenter Server and must be backed up by VDP as well. Only the virtual machine doing the FLR needs a browser with Flash enabled. The virtual machines may be running different operating systems.
A good correlated resource is http://blogs.vmware.com/vsphere/2014/09/vsphere-data-protection-linux-file-level-restore.html. For more information, see Limitations of vSphere Data Protection File Level Restore (2053871).vSphere Data Protection リストア クライアントへのログインが次のエラーによって失敗する:VDP にログイン クライアントが見つかりませんLimitations of vSphere Data Protection File Level Restore 登录到 vSphere Data Protection 还原客户端失败并显示错误：无法在 VDP 中找到登录客户端