Avamar:使用 vCD UI 登录虚拟机时,vCloud Director DPE 文件级恢复失败,并显示错误“User authentication failed”。
Summary: 使用 vCD UI 记录到虚拟机时,vCloud Director DPE 文件级恢复失败,并显示错误“User authentication failed”。 使用 Avamar Administrator 或 AUI 完成时,相同类型的恢复将成功。
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
使用 vCD UI 在虚拟机上启动 FLR 并输入虚拟机凭据时,该过程失败,并显示错误消息“User authentication failed”:
从 DPE 端,可以在 SRV 日志中识别身份验证错误:/var/log/vcp/srv/vcpserver.log:
也可以在备份网关日志中观察到相同的身份验证错误:/var/log/vcp/bg//vcpbg.log:
如果直接使用 Avamar AUI 或 Avamar Administrator 执行相同的虚拟机凭据,则文件级恢复 (FLR) 操作成功。
从 DPE 端,可以在 SRV 日志中识别身份验证错误:/var/log/vcp/srv/vcpserver.log:
2023-04-25 07:50:57,613 [AMQP listener 7] INFO (AdsClient.java:692) - Started connecting FLR destination VM ...
2023-04-25 07:50:57,625 [AMQP listener 7] INFO (RestTemplateFactory.java:125) - POST https://sv-2000avu55.ebrc8002.cloud:8443/vcp-ba-ads-ws/flrDestinationBrowseConnection
2023-04-25 07:51:01,341 [eventListenerContainer-1] INFO (EventListener.java:214) - NOTIFICATION: com/vmware/vcloud/event/task/complete
2023-04-25 07:51:01,363 [AMQP listener 7] ERROR (VcpBaseMessageHandler.java:164) - REQUEST : POST /api/vApp/vapp-17b030c9-c633-4ca3-a245-597ba5e46d7b/vm/vm-3ecd2a2d-6a81-49dd-a79f-ea4815733
96f/connections
2023-04-25 07:51:01,363 [AMQP listener 7] ERROR (VcpBaseMessageHandler.java:165) - HTTP 500 :
com.emc.vcp.service.exceptions.AdsClientException: 11023 : User authentication failed: Invalid guest login
at com.emc.vcp.ads.client.RestTemplateFactory.handleException(RestTemplateFactory.java:239) ~[classes!/:19.7.0.90]
at com.emc.vcp.ads.client.AdsClient.connectDestinationVM(AdsClient.java:699) ~[classes!/:19.7.0.90]
at com.emc.vcp.service.VAppService.onFlrBrowseDestinationConnectionsPOST(VAppService.java:1294) ~[classes!/:19.7.0.90]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_301]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_301]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_301]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_301]
也可以在备份网关日志中观察到相同的身份验证错误:/var/log/vcp/bg//vcpbg.log:
2023-04-25 07:50:57,748 [https-jsse-nio-8443-exec-1] INFO (LoggerInterceptor.java:30) - POST: /vcp-ba-ads-ws/flrDestinationBrowseConnection
2023-04-25 07:50:57,808 [https-jsse-nio-8443-exec-1] INFO (TaskUpdates.java:121) - Updating Task as running : Task Status : running, Operation : FLR: Connecting Destination Virtual Machi
ne (3ecd2a2d-6a81-49dd-a79f-ea481573396f), Operation StartTime : 2023-04-25T07:50:49.797Z, Progress : 10, Cancel Requested : false, Error : null ,
2023-04-25 07:50:58,338 [https-jsse-nio-8443-exec-1] INFO (QueryVCenter.java:99) - Connections to VCenters: 1
2023-04-25 07:51:00,993 [vcp-ads-1] INFO (ServiceADS.java:175) - Running Restore Tracker Task..
2023-04-25 07:51:00,994 [vcp-ads-1] INFO (AdsServices.java:640) - Restore tracker is empty. No pending restores.
2023-04-25 07:51:01,262 [https-jsse-nio-8443-exec-1] INFO (TaskUpdates.java:72) - Updating Task with error : Task Status : error, Operation : FLR: Connecting Destination Virtual Machine
(3ecd2a2d-6a81-49dd-a79f-ea481573396f), Operation StartTime : 2023-04-25T07:50:49.797Z, Progress : 10, Cancel Requested : false, Error : com.vmware.vcloud.api.rest.schema.ErrorType@319778f7
,
2023-04-25 07:51:01,336 [https-jsse-nio-8443-exec-1] ERROR (AdsServices.java:2111) -
com.vmware.vim25.InvalidGuestLogin: Failed to authenticate with the guest operating system using the supplied credentials.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_301]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) ~[?:1.8.0_301]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) ~[?:1.8.0_301]
at java.lang.reflect.Constructor.newInstance(Unknown Source) ~[?:1.8.0_301]
at java.lang.Class.newInstance(Unknown Source) ~[?:1.8.0_301]
at com.vmware.vim25.ws.XmlGenDom.fromXml(XmlGenDom.java:253) ~[yavijava-6.0.05.jar!/:?]
at com.vmware.vim25.ws.XmlGenDom.parseSoapFault(XmlGenDom.java:151) ~[yavijava-6.0.05.jar!/:?]
at com.vmware.vim25.ws.XmlGenDom.fromXML(XmlGenDom.java:109) ~[yavijava-6.0.05.jar!/:?]
at com.vmware.vim25.ws.SoapClient.unMarshall(SoapClient.java:253) ~[yavijava-6.0.05.jar!/:?]
at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:96) ~[yavijava-6.0.05.jar!/:?]
at com.vmware.vim25.ws.VimStub.validateCredentialsInGuest(VimStub.java:4554) ~[yavijava-6.0.05.jar!/:?]
at com.vmware.vim25.mo.GuestAuthManager.ValidateCredentialsInGuest(GuestAuthManager.java:70) ~[yavijava-6.0.05.jar!/:?]
如果直接使用 Avamar AUI 或 Avamar Administrator 执行相同的虚拟机凭据,则文件级恢复 (FLR) 操作成功。
Cause
密码包含加号 (+),导致 vCD UI 上的虚拟机身份验证失败。
这是一个 DPE 问题,目前正在与工程部门一起调查。
这是一个 DPE 问题,目前正在与工程部门一起调查。
Resolution
解决 方案:
有两种可能的解决方法可用。尝试一个或另一个:
1。直接从 Avamar UI 尝试 FLR。
有两种可能的解决方法可用。尝试一个或另一个:
1。直接从 Avamar UI 尝试 FLR。
2.将虚拟机密码中的 + 字符更改为另一个符号。
修复:
请联系戴尔支持,并引用本文以检查工程调查的当前状态。修复:
Affected Products
vCloud Director Data Protection ExtensionArticle Properties
Article Number: 000214288
Article Type: Solution
Last Modified: 23 Aug 2023
Version: 2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.