未解决
此帖子已超过 5 年
7 消息
0
2594
Avamar + DataDomain 备份VMware虚拟机报错啦，求解决方案
Hi all，
一个项目中Avamar + DataDomain 备份VMware虚拟机报错啦，800 说是VMware上的配置问题，求解决方案，报错日志如下：
Summary
Log Files
Log #1: avvcbimage log 2013-05-24 15:40:44 CST [6.1.101-87 Linux-x86_64] (4 errors)
Log #2: MOD-1369381016227 log 2013-05-24 15:40:44 CST [6.1.101-87 Linux-x86_64]
Errors and Exceptions
2013-05-24 15:40:44 avvcbimage Error <14618>: Problem logging into URL 'https://10.130.34.150:443/sdk' with user 'Administrator' (Log #1)
2013-05-24 15:40:44 avvcbimage Error <14618>: Problem logging into URL 'https://10.130.34.150:443/sdk' with user 'Administrator' (Log #1)
2013-05-24 15:40:46 avvcbimage Error <14618>: Problem logging into URL 'https://10.130.34.150:443/sdk' with user 'Administrator' (Log #1)
2013-05-24 15:40:46 avvcbimage Error <9759>: createSnapshot: snapshot creation failed (Log #1)
*********** /usr/local/avamarclient/var-proxy-1/MOD-1369381016227-7c6805bae65a0b9fbaa4d0cfb55e1a11cf4abbe8-3016-vmimagew.log ***********
Log #1: avvcbimage log 2013-05-24 15:40:44 CST [6.1.101-87 Linux-x86_64]
2013-05-24 15:40:44 avvcbimage Info <5008>: Logging to /usr/local/avamarclient/var-proxy-1/MOD-1369381016227-7c6805bae65a0b9fbaa4d0cfb55e1a11cf4abbe8-3016-vmimagew.log 2013-05-24 15:40:44 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var-proxy-1/avvcbimage.cmd 2013-05-24 15:40:44 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd 2013-05-24 15:40:44 avvcbimage Info <6673>: CTL listening on port 58941 2013-05-24 15:40:44 avvcbimage Info <10684>: Setting ctl message version to 3 (from 1) 2013-05-24 15:40:44 avvcbimage Info <16136>: Setting ctl max message size to 268435456 2013-05-24 15:40:44 avvcbimage Info <16005>: Login(https://10.130.34.150:443/sdk) problem with reused sessionID='A752868C-FA46-463B-8311-8EF235CA0ACD' contacting data center '港湾IDC VM群集'. 2013-05-24 15:40:44 avvcbimage Warning <16020>: Problem logging into URL 'https://10.130.34.150:443/sdk' with session cookie. 2013-05-24 15:40:44 avvcbimage Info <16021>: Logging into URL 'https://10.130.34.150:443/sdk' with user 'Administrator' credentials. 2013-05-24 15:40:44 avvcbimage Info <14678>: Login(https://10.130.34.150:443/sdk) problem with sessionID='B5135AB8-2074-4EE8-9003-D63BD503DF0B' contacting data center '港湾IDC VM群集'. 2013-05-24 15:40:44 avvcbimage Error <14618>: Problem logging into URL 'https://10.130.34.150:443/sdk' with user 'Administrator' 2013-05-24 15:40:44 avvcbimage Info <14625>: WorkOrder Disk Info: Disk '2000': file(base):'[datastore1] ssr_client_win2003/ssr_client_win2003.vmdk', backItUp=1 snapshot file:'[datastore1] ssr_client_win2003/ssr_client_win2003.vmdk' prior size(KB):0, current size(KB):31457280, match=0 change block ID:'' 2013-05-24 15:40:44 avvcbimage Info <11979>: proxy VM DNS name is: 127.0.0.2,10.130.34.56 2013-05-24 15:40:44 avvcbimage Info <16010>: vCenter '港湾IDC VM群集' is 10.130.34.150 2013-05-24 15:40:44 avvcbimage Info <11981>: VM's host is 192.168.128.218 2013-05-24 15:40:44 avvcbimage Info <11982>: VM's primary storage location is [datastore1] ssr_client_win2003/ssr_client_win2003.vmx 2013-05-24 15:40:44 avvcbimage Info <11983>: VM's vCenter ID is vm-19 2013-05-24 15:40:44 avvcbimage Info <11984>: VM's backup account on SLXCNDCZ01AVA01.cz.aac.com is /10.130.34.150/Uifu4Q2XjiAsi4x5uxRlEg 2013-05-24 15:40:44 avvcbimage Info <11991>: VM does NOT have changed block detection enabled. This will increase proxy CPU and IOP consumption. 2013-05-24 15:40:44 avvcbimage Info <16005>: Login(https://10.130.34.150:443/sdk) problem with reused sessionID='A752868C-FA46-463B-8311-8EF235CA0ACD' contacting data center '港湾IDC VM群集'. 2013-05-24 15:40:44 avvcbimage Warning <16020>: Problem logging into URL 'https://10.130.34.150:443/sdk' with session cookie. 2013-05-24 15:40:44 avvcbimage Info <16021>: Logging into URL 'https://10.130.34.150:443/sdk' with user 'Administrator' credentials. 2013-05-24 15:40:44 avvcbimage Info <14678>: Login(https://10.130.34.150:443/sdk) problem with sessionID='55FDFA1F-87BA-4954-8D78-1AADAD964960' contacting data center '港湾IDC VM群集'. 2013-05-24 15:40:44 avvcbimage Error <14618>: Problem logging into URL 'https://10.130.34.150:443/sdk' with user 'Administrator' 2013-05-24 15:40:44 avvcbimage Info <5174>: - Reading usr/local/avamarclient/var-proxy-1/avvcbimage.cmd 2013-05-24 15:40:44 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd 2013-05-24 15:40:44 avvcbimage Info <7084>: target[0]=[datastore1] ssr_client_win2003/ssr_client_win2003.vmdk 2013-05-24 15:40:44 avvcbimage Info <16041>: VDDK:VixDiskLib: linuxVerifySSLCertificates is 0 2013-05-24 15:40:44 avvcbimage Info <16041>: VDDK:VixDiskLib: config options: libdir '/usr/lib/vmware-vix-disklib', tmpDir '/usr/local/avamarclient/var-proxy-1/vmware/temp'. 2013-05-24 15:40:44 avvcbimage Info <16041>: VDDK:OBJLIB-LIB : Objlib initialized. 2013-05-24 15:40:44 avvcbimage Info <16041>: VDDK:VixDiskLib: Attempting to locate advanced transport module in "/usr/lib/vmware-vix-disklib". 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:VixDiskLib: Advanced transport plugin was successfully loaded into vixDiskLib. 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:VixDiskLib: Enabling advanced transport modes. 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:OBJLIB-LIB : Objlib initialized. 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:VixDiskLib: Transport modes available: file:nbdssl:nbd:san. 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:VMware VixDiskLib (5.1) Release build-774844 2013-05-24 15:40:45 avvcbimage Info <9666>: Available transport modes are file:san:hotadd:nbdssl:nbd 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:VixDiskLibVimResolveHostName: Resolving IP address for hostname 10.130.34.150:443. 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:VixDiskLibVimResolveHostName: Resolved to 10.130.34.150. 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLogin 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:VixDiskLibVim: TicketFindVMByMoRef: vmxPath = -vm-19- 2013-05-24 15:40:45 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLoadVM 2013-05-24 15:40:46 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLoadAuthMgr 2013-05-24 15:40:46 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLoadVMCb 2013-05-24 15:40:46 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLogout 2013-05-24 15:40:46 avvcbimage Info <0000>: VixDiskLib vMotion reservation successfully enabled by 'EMC Avamar VM Backup Proxy' 2013-05-24 15:40:46 avvcbimage Info <16011>: Running cleanup of old backups. 2013-05-24 15:40:46 avvcbimage Info <16048>: VixDiskLib_Cleanup() found no prior mounts to cleanup. 2013-05-24 15:40:46 avvcbimage Info <16005>: Login(https://10.130.34.150:443/sdk) problem with reused sessionID='A752868C-FA46-463B-8311-8EF235CA0ACD' contacting data center '港湾IDC VM群集'. 2013-05-24 15:40:46 avvcbimage Warning <16020>: Problem logging into URL 'https://10.130.34.150:443/sdk' with session cookie. 2013-05-24 15:40:46 avvcbimage Info <16021>: Logging into URL 'https://10.130.34.150:443/sdk' with user 'Administrator' credentials. 2013-05-24 15:40:46 avvcbimage Info <14678>: Login(https://10.130.34.150:443/sdk) problem with sessionID='AF3EAEB9-4724-4C3F-A561-B7567299EE05' contacting data center '港湾IDC VM群集'. 2013-05-24 15:40:46 avvcbimage Error <14618>: Problem logging into URL 'https://10.130.34.150:443/sdk' with user 'Administrator' 2013-05-24 15:40:46 avvcbimage Error <9759>: createSnapshot: snapshot creation failed 2013-05-24 15:40:46 avvcbimage Info <14696>: snapshot created:false NOMC:false ChangeBlTrackingAvail:false UsingChBl:true, FullBackup=true 2013-05-24 15:40:46 avvcbimage Info <9666>: Available transport modes are file:san:hotadd:nbdssl:nbd 2013-05-24 15:40:46 avvcbimage Info <9667>: Calling ConnectEx with servername=10.130.34.150:443 vmxspec=moref=vm-19 on port 0 snapshot() 2013-05-24 15:40:46 avvcbimage Info <9668>: virtual machine will be connected readonly 2013-05-24 15:40:46 avvcbimage Info <9669>: VixDiskLib_ConnectEx returned VIX_OK 2013-05-24 15:40:46 avvcbimage Info <0000>: Starting graceful (staged) termination, a VM problem occurred in the backup (wrap-up stage) 2013-05-24 15:40:46 avvcbimage Info <9672>: Disconnected from VM 2013-05-24 15:40:46 avvcbimage Info <16041>: VDDK:VixDiskLibVimResolveHostName: Resolving IP address for hostname 10.130.34.150:443. 2013-05-24 15:40:46 avvcbimage Info <16041>: VDDK:VixDiskLibVimResolveHostName: Resolved to 10.130.34.150. 2013-05-24 15:40:46 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLogin 2013-05-24 15:40:46 avvcbimage Info <16038>: Final summary, cancelled/aborted 0, snapview 1, exitcode 207: plugin error 07 2013-05-24 15:40:47 avvcbimage Info <16041>: VDDK:VixDiskLibVim: TicketFindVMByMoRef: vmxPath = -vm-19- 2013-05-24 15:40:47 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLoadVM 2013-05-24 15:40:47 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLoadAuthMgr 2013-05-24 15:40:47 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLoadVMCb 2013-05-24 15:40:48 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLogout 2013-05-24 15:40:48 avvcbimage Info <0000>: VixDiskLib vMotion reservation successfully released
END avvcbimage log 2013-05-24 15:40:51 CST (3 warnings, 4 errors, 0 fatal errors)
*********** /usr/local/avamarclient/var-proxy-1/MOD-1369381016227-7c6805bae65a0b9fbaa4d0cfb55e1a11cf4abbe8-3016-vmimagew.alg ***********
Log #2: MOD-1369381016227 log 2013-05-24 15:40:44 CST [6.1.101-87 Linux-x86_64]
2013-05-24 15:40:44 MOD-1369381016227 Info <0000>: [agent_ctl_sup] Workorder : MOD-1369381016227 2013-05-24 15:40:44 MOD-1369381016227 Info <0000>: [agent_ctl_sup] Plugin ID : 3016-vmimagew 2013-05-24 15:40:44 MOD-1369381016227 Info <0000>: [agent_ctl_sup] bindir : /usr/local/avamarclient/bin 2013-05-24 15:40:44 MOD-1369381016227 Info <0000>: [agent_ctl_sup] vardir : /usr/local/avamarclient/var-proxy-1 2013-05-24 15:40:44 MOD-1369381016227 Info <0000>: [agent_ctl_sup] Initiator : 2013-05-24 15:40:44 MOD-1369381016227 Info <0000>: [ctl_spawn] Executable : /usr/local/avamarclient/bin/avvcbimage 2013-05-24 15:40:44 MOD-1369381016227 Info <0000>: [ctl_spawn] Args : avvcbimage --sysdir="/usr/local/avamarclient/etc" --bindir="/usr/local/avamarclient/bin" --vardir="/usr/local/avamarclient/var-proxy-1" --ctlcallport="38883" --ctlinterface="3016-vmimagew-MOD-1369381016227" --logfile="/usr/local/avamarclient/var-proxy-1/MOD-1369381016227-7c6805bae65a0b9fbaa4d0cfb55e1a11cf4abbe8-3016-vmimagew.log" 2013-05-24 15:40:44 MOD-1369381016227 Info <0000>: [agent_ctl_sup] Order : 2013-05-24 15:40:52 MOD-1369381016227 Info <0000>: [ctl_spawn] 2013-05-24 07:40:44" msgver="1" pidnum="3016" finishUTC="2013-05-24 07:40:52" errorcode="0" wid="MOD-1369381016227" errormessage="code 0: success" errorrealm="Plugin 3016-vmimagew" />
jiaguo_store
7 消息
0
2013年5月24日 07:00
自己先顶一下，很着急，客户的VMware是4.1 Avamar是6.1 DD OS是5.2.2
Jason_Zhou
2 Intern
2 Intern
•
1.2K 消息
0
2013年6月7日 20:00
wang jiaguo ，你好。我是论坛版主Jason周。我注意到，你的这个帖子被不小心创建在了你的个人的版面内了，所以大家根本都没看到，也当然至今也没回复。至于为什么会发生这样的情况以及如何避免，可参考我写的这个帖子 【帮助说明】如何避免帖子在不经意间被创建在了错误的版面里，导致收不到回复（因为别人看不到帖子）
我现在已把你的帖子移动到中文支持论坛内的 备份和恢复系统 版块里了，稍后会有懂Avamar和DD的朋友来跟你分享或解答。以后建议先由中文支持论坛首页 用顶部的导航按钮先进入相应的版块，然后用右边操作栏里的“开始一个讨论”来创建帖子提问或者分享，这样创建出来的帖子默认就是在你所在的版块的，避免帖子被无意中创建在了个人版块内
born_chen
2 Intern
2 Intern
•
1.8K 消息
0
2013年6月7日 21:00
参考这个帖子。
Re: Avamar Backups using vmdk
还有这份材料。看样子是版本太旧。
One of my customers recently had the same issue. After contacting EMC support this was the response,
o17Uu33DCF12520
2 Intern
2 Intern
•
1.1K 消息
0
2013年6月7日 22:00
楼主，你连接的两个日志都是指向qq.com，从EMC内网是无法直接访问的。
你方便直接使用论坛的附件功能上传么？
如果比较急，建议直接开case联系在线支持比较快