未解决
1 Rookie
•
15 消息
0
723
avamar备份虚拟机，其中一台报错无法创建快照
avamar备份虚拟机，其中一台报错无法创建快照，
Summary
Log Files
Log #1:/usr/local/avamarclient/var/MOD-1667446305496-b37c2ab43917bc9ca9edeeace741fab796bcaaaf-3016-vmimagew-xmlstats.log
Log #2:avvcbimage log 2022-11-03 11:37:20 CST [19.1.100-38 Linux-x86_64] (3 errors)
Log #3:MOD-1667446305496 log 2022-11-03 11:37:20 CST [19.1.100-38 Linux-x86_64]
Errors and Exceptions
2022-11-03 11:37:40 avvcbimage FATAL <0000>: [IMG0002] The datastore information from VMX '[Vplex-Unity400-1.8-4.5T] Queueing/Queueing.vmx' will not permit a restore or backup. (Log #2)
2022-11-03 11:37:40 avvcbimage Error <0000>: [IMG0009] Create Snapshot: snapshot creation or pre/post snapshot script failed. (Log #2)
2022-11-03 11:37:40 avvcbimage Error <0000>: [IMG0009] Create Snapshot: snapshot creation/pre-script/post-script failed. (Log #2)
*********** /usr/local/avamarclient/var/MOD-1667446305496-b37c2ab43917bc9ca9edeeace741fab796bcaaaf-3016-vmimagew-xmlstats.log ***********
Log #1: /usr/local/avamarclient/var/MOD-1667446305496-b37c2ab43917bc9ca9edeeace741fab796bcaaaf-3016-vmimagew-xmlstats.log
192.168.80.53
6.7.0
17137327
avamarproxy-proxy-3
19.1.100-38
192.168.80.46
6.7.3 build-17499825
*********** /usr/local/avamarclient/var/MOD-1667446305496-b37c2ab43917bc9ca9edeeace741fab796bcaaaf-3016-vmimagew.log ***********
Log #2: avvcbimage log 2022-11-03 11:37:20 CST [19.1.100-38 Linux-x86_64]
2022-11-03 11:37:20 avvcbimage Info <5008>: Logging to /usr/local/avamarclient/var/MOD-1667446305496-b37c2ab43917bc9ca9edeeace741fab796bcaaaf-3016-vmimagew.log
2022-11-03 11:37:20 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimage.cmd
2022-11-03 11:37:20 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd
2022-11-03 11:37:20 avvcbimage Info <6673>: CTL listening on port 54430
2022-11-03 11:37:20 avvcbimage Info <10684>: Setting ctl message version to 3 (from 1)
2022-11-03 11:37:20 avvcbimage Info <16136>: Setting ctl max message size to 268435456
2022-11-03 11:37:20 avvcbimage Info <40636>: SSL Certificate Thumbprint: 1F:27:81:D5:87:D6:B0:1D:AD:12:7F:9B:3B:B7:A4:CB:FD:E4:41:C4
2022-11-03 11:37:20 avvcbimage Info <42665>: setParent(): sGuestName= sProxyHostName=avamarproxy svCentername=192.168.80.53 sGuestVmName=Queueing.30.27 sVmxPath=[Vplex-Unity400-1.8-4.5T] Queueing/Queueing.vmx
2022-11-03 11:37:20 avvcbimage Info <43574>: vcApiVersion 6.5
2022-11-03 11:37:20 avvcbimage Info <43575>: VSphereHTTP::vcVersion65 will be true
2022-11-03 11:37:20 avvcbimage Info <42137>: job type = 4
2022-11-03 11:37:20 avvcbimage Info <18664>: Login(https://192.168.80.53:443/sdk) Datacenter: 'A-A-Datacenter'
2022-11-03 11:37:20 avvcbimage Info <19728>: - connected to 'VirtualCenter' - version: 'VMware vCenter Server 6.7.0 build-17137327', apiVersion:'6.7.3'
2022-11-03 11:37:20 avvcbimage Info <42146>: Login by loginWS test is OK.
2022-11-03 11:37:30 avvcbimage Info <40726>: VM Config Info: VMX version 4(F), ctk enabled(T), fault tolerant (F), Guest OS Microsoft Windows Server 2008 R2 (64-bit), Cloud UUID = NoUUID. version=13
2022-11-03 11:37:30 avvcbimage Info <40727>: VM Guest Info: GuestOS Family = windowsGuest, Guest Full Name = Microsoft Windows Server 2008 R2 (64-bit), Guest OS State = running, Tools Running = guestToolsRunning, Tools Version Status = guestToolsCurrent
2022-11-03 11:37:30 avvcbimage Info <14625>: WorkOrder Disk Info:
Prior Disk '2000': file(base):'[Vplex-Unity400-1.8-4.5T] Queueing/Queueing.vmdk', backItUp=1
snapshot file:'[Vplex-Unity400-1.8-4.5T] Queueing/Queueing.vmdk'
prior size(KB):0, current size(KB):314572800, match=0
prior change block ID:''
Datastore:'Vplex-Unity400-1.8-4.5T' Directly Accessible=1
2022-11-03 11:37:30 avvcbimage Info <40637>: Proxy Host Name=192.168.80.19(6.7.3 build-17499825)
2022-11-03 11:37:30 avvcbimage Info <40638>: VM Host Name=192.168.80.46(6.7.3 build-17499825)
2022-11-03 11:37:30 avvcbimage Info <19547>: Using Simultaneous Workorders method
2022-11-03 11:37:30 avvcbimage Info <19652>: Updated cache lookup
2022-11-03 11:37:30 avvcbimage Info <19587>: Create cache lock file succeeded
2022-11-03 11:37:30 avvcbimage Info <19588>: usLockFile: /usr/local/avamarclient/bin/var3.lck
2022-11-03 11:37:37 avvcbimage Info <11979>: proxy VM DNS name is: 192.168.80.62,avamarproxy,localhost,ipv6-localhost,ipv6-loopback,::1,fe80::250:56ff:fe8a:2501
2022-11-03 11:37:37 avvcbimage Info <18672>: proxy VM Instance name is: avamarproxy-proxy-3
2022-11-03 11:37:37 avvcbimage Info <17793>: proxy VM Moref is: vm-45847
2022-11-03 11:37:37 avvcbimage Info <16010>: vCenter 'A-A-Datacenter' is 192.168.80.53
2022-11-03 11:37:37 avvcbimage Info <11981>: VM's host is 192.168.80.46
2022-11-03 11:37:37 avvcbimage Info <11982>: VM's primary storage location is [Vplex-Unity400-1.8-4.5T] Queueing/Queueing.vmx
2022-11-03 11:37:37 avvcbimage Info <11983>: VM's vCenter ID is vm-178
2022-11-03 11:37:37 avvcbimage Info <19658>: change block file: VmImage3_changefilemap.tmp
2022-11-03 11:37:37 avvcbimage Info <11984>: VM's backup account on 192.168.80.55 is /192.168.80.53/ContainerClients/Queueing.30.27_C2AR7BAcMQ2WCIPPqg83JA
2022-11-03 11:37:37 avvcbimage Info <11986>: Changed block tracking is engaged for this VM
2022-11-03 11:37:37 avvcbimage Info <11988>: A reference to a valid prior backup is not available so this will be a full level zero backup.
2022-11-03 11:37:37 avvcbimage Info <19549>: metadata tmp dir: /usr/local/avamarclient/var/vmware/3/temp
2022-11-03 11:37:37 avvcbimage Info <40640>: create tmpDir: /usr, failed (-1)
2022-11-03 11:37:37 avvcbimage Info <40640>: create tmpDir: /usr/local, failed (-1)
2022-11-03 11:37:37 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient, failed (-1)
2022-11-03 11:37:37 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var, failed (-1)
2022-11-03 11:37:37 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var/vmware, failed (-1)
2022-11-03 11:37:37 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var/vmware/3, failed (-1)
2022-11-03 11:37:37 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var/vmware/3/temp, failed (-1)
2022-11-03 11:37:37 avvcbimage Info <40654>: isExitOK()=0
2022-11-03 11:37:37 avvcbimage Info <17823>: Body- abortrecommended(f)
2022-11-03 11:37:37 avvcbimage Info <19660>: targetlist contains
END avvcbimage log 2022-11-03 11:37:46 CST (3 warnings, 3 errors, 1 fatal error)
*********** /usr/local/avamarclient/var/MOD-1667446305496-b37c2ab43917bc9ca9edeeace741fab796bcaaaf-3016-vmimagew.alg ***********
Log #3: MOD-1667446305496 log 2022-11-03 11:37:20 CST [19.1.100-38 Linux-x86_64]
2022-11-03 11:37:20 MOD-1667446305496 Info <0000>: Workorder : MOD-1667446305496
2022-11-03 11:37:20 MOD-1667446305496 Info <0000>: Plugin ID : 3016-vmimagew
2022-11-03 11:37:20 MOD-1667446305496 Info <0000>: bindir : /usr/local/avamarclient/bin
2022-11-03 11:37:20 MOD-1667446305496 Info <0000>: vardir : /usr/local/avamarclient/var
2022-11-03 11:37:20 MOD-1667446305496 Info <0000>: Initiator :
2022-11-03 11:37:20 MOD-1667446305496 Info <0000>: Executable : /usr/local/avamarclient/bin/avvcbimage
2022-11-03 11:37:20 MOD-1667446305496 Info <0000>: Args : avvcbimage --sysdir="/usr/local/avamarclient/etc" --bindir="/usr/local/avamarclient/bin" --vardir="/usr/local/avamarclient/var" --ctlcallport="57831" --ctlinterface="3016-MOD-1667446305496-b37c2ab43917bc9ca9edeeace741fab796bcaaaf" --logtimeformat="default" --logtimezone="default" --logfile="/usr/local/avamarclient/var/MOD-1667446305496-b37c2ab43917bc9ca9edeeace741fab796bcaaaf-3016-vmimagew.log" --ctlusessl="true"
2022-11-03 11:37:20 MOD-1667446305496 Info <0000>: Order :
DELL-Leo
Community Manager
Community Manager
•
7.1K 消息
0
2022年11月3日 23:00
您好！
这个问题和您之前发的下面的问题是同一个问题是吗？问题已经解决了是吧。
https://www.dell.com/community/%E6%95%B0%E6%8D%AE%E4%BF%9D%E6%8A%A4%E8%AE%A8%E8%AE%BA%E5%8C%BA/all-virtual-machines-backup-failed%E6%89%80%E6%9C%89%E8%99%9A%E6%8B%9F%E6%9C%BA%E5%A4%87%E4%BB%BD%E9%83%BD%E6%8F%90%E7%A4%BA%E6%97%A0%E6%B3%95%E5%88%9B%E5%BB%BA%E5%BF%AB%E7%85%A7/m-p/8291819#M7005
dangdang_togo
1 Rookie
1 Rookie
•
15 消息
0
2022年11月8日 02:00
不是同一个问题，之前是所有虚拟机都无法备份，现在只有一台
DELL-Leo
Community Manager
Community Manager
•
7.1K 消息
0
2022年11月9日 01:00
您好！
请参考看下面的内容来解决：
VMWare Image Backups Fail (Code 10056) >> avvcbimage Error <9759>: createSnapshot: Snapshot creation failed
Unable to perform VMware client Image backups and they are failing with Code 10056.
The Snapshot create task fails with the following errors:
Issue #1
avvcbimage Warning <16002>: Too many extra snapshot files (3) were found on the VMs datastore. This can cause a problem for the backup or restore.
avvcbimage FATAL <16018>: The datastore information from VMX '[MLUN] Datastore/TestMachine.vmx' will not permit a restore or backup.
avvcbimage Info <0000>: Starting graceful (staged) termination, Too many pre-existing snapshots on the datastore will not permit a restore or backup. (wrap-up stage)
avvcbimage Error <9759>: createSnapshot: snapshot creation failed
The log shows Avamar did not detect there is Snapshot for this VM initially:
avvcbimage Info <14664>: no snapshots are present on this VM.However, there are Snapshot files on the Datastore:
2013-01-31 23:37:54 avvcbimage Info <14677>: All VM file Info:File:'CCHA-00SV0D0SAN-000003-ctk.vmdk ' last modified on '07-Dec-2011 15:58' size=3932672
File:'CCHA-00SV0D0SAN-000003-delta.vmdk ' last modified on '07-Dec-2011 15:57' size=134344704
File:'CCHA-00SV0D0SAN-000003.vmdk ' last modified on '07-Dec-2011 15:55' size=408
Issue #2 The vm has too many existing snapshots (30 or more)2015-02-20 13:47:23 avvcbimage Info <14665>: 30 snapshots are present on this VM:
level=1, children=1, ref='snapshot-4223', 'snapshot1':desc='na'
...
*level=30, children=0, ref='snapshot-4252', 'snapshot30':desc='na
2015-02-20 13:47:23 avvcbimage FATAL <0000>: [IMG0019] The pre-existing snapshots from VMX '[MLUN] Datastore/TestMachine.vmx does not permit a backup.
System: VMWare
For issue #1If there are Snapshot files in the Virtual Machine directory and vCenter reported less then was discovered by the scan then the backup fails.
When Avamar attempts to backup a Virtual Machine, it must take a snapshot. Before performing it queries vCenter for how many snapshots the Virtual Machine currently contains. Then the Datastore directory is scanned where the Virtual Machine resides.
For Issue #2VMware ESI will only permit up to 32 before the Snapshot task fails with: Create Virtual Machine Sapshot task fails with a VMware error of: "Snapshot hierarchy is too deep". As described above we need to take a new "Avamar" snapshot (bring Snapshot count to 31). And the end of the backup we need to delete this Snapshot. This delete action causes ESX to create a hidden esx Snapshot called consolidated helper (snapshot count would be 32) and could fail due to the ESX "Snapshot hierarchy is too deep" issue. For this reason the Avamar proxy code will NOT allow Snapshots of a VM that has existing 30 snapshots.
For Issue #1Snapshot files must be removed from the Virtual Machines Datastore Directory.
Before removing the files there are some checks that must be completed.
For Issue #2.
In VMware, delete the existing Snapshot. VMware does not recommend using Snapshots as your only backup strategy (For example: use product like Avamar ). Have more than a small set of short term Snapshots that introduces latency and high stun times during Snapshot operations.Ideally a VM should not have Snapshot.