Unsolved
This post is more than 5 years old
8 Posts
0
36514
vmware image backups failing - error code 10013
I'm trying to get the VMware image backups working...
And in fact, if I shut down the VM I'm trying to back up, it works just fine.
However, if the VM is running, I get errors in vSphere saying it's unable access vmname/vmname.vmx... and also vmname/vmname.nvram
Then it fails. The Activity log in the avamar administrator shows "Cancelled" and "10013" as the error code.
I tried manually copying this file to another location on the same datastore using the vSphere client, and it also fails with the same error (in vSphere)... "unable to access file..."
If I manually snapshot a VM using the vSphere client, the snapshot works just fine.
Any help on this would be appreciated.
rpervan
266 Posts
0
April 27th, 2010 01:00
High Level Cause:
Four Possible Root Causes:
Possible Root Cause #1: Failed to get VMware vCenter connection
Workaround/Solution:
Workaround/Solution:
+ %2B
/ %2F
= %3D
? %3F
% %25
\ %5C
~ %7E
] %5D
Workaround/Solution:
Workaround/Solution:
Value : 8192
This allows the backup to complete even if the vmx file (that contains the VM configuration) is not backed up.
Because the VM configuration information is NOT backed up (if the .vmx file is 0 bytes), the following will apply during the restore process: The restore for this backup will work for restore to original and restore to existing, but not for restore to new. To do restore to new, you need to manually create a VM with the same configuration as the original VM, and do restore to existing to the newly created VM.
manivas
18 Posts
0
May 25th, 2010 22:00
This issue is tracked by VMware under VMware Support Request SR# 1483856391. This issue is also being tracked under Avamar bug 17608.
Any update on this?.
markaldridge
9 Posts
0
May 26th, 2010 08:00
I have started the RPQ process with EMC to qualify the ISCSI storage. In the mean time we wait for the VMware patch im afraid.
matej_felle
41 Posts
0
June 9th, 2010 01:00
We have the same problem at our customer .....
This is VMware ESX 4 issue .... It will be fix in VMware ESX 4 update 2 ....
BR
jboitel
18 Posts
0
June 17th, 2010 09:00
I updated my ESX4 to update2 and now, the image-level backup doesn't work !
When I backup a VM, I can see a "reconfigure" of my VM in Virtual Center, and after nothing ! no snapshot...
The Avamar activity show a "Time Out Response !"
Before, in ESX4 Update 1, the backups were almost OK (sometimes, I had locked vmx, but it worked better).
Somebody who has an idea ???
rpervan
266 Posts
0
June 21st, 2010 05:00
High Level Cause:
Four Possible Root Causes:
Possible Root Cause #1: Failed to get VMware vCenter connection
Workaround/Solution:
Workaround/Solution:
+ %2B
/ %2F
= %3D
? %3F
% %25
\ %5C
~ %7E
] %5D
Workaround/Solution:
Workaround/Solution:
Value : 8192
This allows the backup to complete even if the vmx file (that contains the VM configuration) is not backed up.
Because the VM configuration information is NOT backed up (if the .vmx file is 0 bytes), the following will apply during the restore process: The restore for this backup will work for restore to original and restore to existing, but not for restore to new. To do restore to new, you need to manually create a VM with the same configuration as the original VM, and do restore to existing to the newly created VM.
nwilliams2
2 Posts
0
July 8th, 2010 13:00
Confirmed that this worked for me.
The workaround is pass the following option into the avvcbimage plugin: --x22=8192
Hormigo
131 Posts
0
July 8th, 2010 15:00
Hi,
Resolved all problems with this configuration:
Update all for:
VMWare vSphere 4 Update 2 (build 258672)
Avamar Server 5.0.2.41
Avamar VM Proxy 5.0.105-169 (Included with SP2 on the Grid)
Regards,
Hormigo
Allbertik
38 Posts
0
January 31st, 2014 01:00
Hello, i have problem too :
2014-01-31 08:38:43 avvcbimage Error <12016>: vmx file is suspiciously small (under 30 bytes), please examine the log on the Avamar Administrator for root cause analysis (Log #2)
2014-01-31 08:38:43 avvcbimage Error <9760>: Backup of VM metadata failed. (Log #2)
2014-01-31 08:38:47 avvcbimage Error <9768>: Avtar exited with 'code 163: externally cancelled' (Log #2)
If I use parameter x22=8192 don't work too.
Avamar Administrator 6.1.2-47
Avamar Combined Proxy-linux-sles11_64-6.1.102-47
vSphere 5.5.0
pawankumawat
355 Posts
0
January 31st, 2014 04:00
Hello Baa,
This issue may occur from different causes. Adding parameter x22=8192 may resolve issue if this issue is caused by Possible Root Cause #4: Unable to retrieve .vmx file because the ESX server has an exclusive lock on the file as mentioned in earlier posts here.
I would suggest you to please open a SR with EMC support to get this issue resolved.
Regards,
Pawan