This post is more than 5 years old
1 Rookie
•
21 Posts
0
30624
May 27th, 2014 11:00
Error Code 10052
I'm getting error code 10052 in my log and the Avamar backup fails on a couple of my VM servers. All it tells me is "The VM could not be snapshot." I can find the error codes in the documentation I have from Avamar, but I haven't been able to find anything about a fix.
Any ideas? Anyone had this and found the resolution?
No Events found!
J_H_
2 Intern
•
498 Posts
0
June 2nd, 2014 12:00
I asked about what version you were running - because there is a KNOWN issue with vCetner 5.5 and avamar 6.x (do not know if it is still an issue with 7.x - as I already had the fix in when I upgraded to 7)
Hadto add this option to the dataset that backups the windows vm's
[avvcbimage]quiesce_fs=false
and that is [ a v v c b i m a g e ]
it has been mentioned a few times before here
dynamox
9 Legend
•
20.4K Posts
0
May 27th, 2014 11:00
yep, seen a ton of these. Ask your VM admin to consolidate snapshots (some are orphaned and not even visible)
dynamox
9 Legend
•
20.4K Posts
0
May 28th, 2014 13:00
your VM is being backed up with a proxy, i have VMs with 1G left on the C drive and have no problems. Check free space in the datastore ?
GNeal11
1 Rookie
•
21 Posts
0
May 28th, 2014 13:00
I don't think it's a snapshot problem. I've consolidated, taken and then done a delete all to commit all snapshots but it still fails.
I think the thing I'm running into is I have little space left on the c: drive and it's failing because of that. I'm running Server 2003 R2 sp2 on the server. What is the best way to extend the drive?
mb_jones
2 Posts
0
May 28th, 2014 13:00
Have you checked your Avamar proxies to verify that they do not have the virtual machines' vDisks still mounted? Go to the proxy VM and click "Edit Settings". Take a look at the vDisks listed for the machine.
GNeal11
1 Rookie
•
21 Posts
0
May 29th, 2014 08:00
I'm talking under a couple hundred megs on a couple of the servers for free space on the c: drives.
Plenty of space in the datastore as well.
GNeal11
1 Rookie
•
21 Posts
0
May 29th, 2014 08:00
vDisks aren't mounted.
dynamox
9 Legend
•
20.4K Posts
0
May 29th, 2014 13:00
do you see anything in the log that says
J_H_
2 Intern
•
498 Posts
0
May 30th, 2014 13:00
what version of vCenter what version of Avamar - was an upgrade done on either recently?
I have also had it where cleaning the snaps did not work but a reboot of the client did.
swakanchar
1 Message
0
June 2nd, 2014 12:00
a few vm backups are failing with error code 10052 and I see the error:
"An error occurred while saving the snapshot: Failed to quiesce the virtual machine."
GNeal11
1 Rookie
•
21 Posts
0
June 2nd, 2014 12:00
dynamox
9 Legend
•
20.4K Posts
1
June 2nd, 2014 12:00
i was experiencing this on 3 VMs last week, had VM admin upgrade VM hardware version (from 7 to 9) and at the same upgraded the VMware tools. So far so good ..no issues with backups.
J_H_
2 Intern
•
498 Posts
0
June 2nd, 2014 13:00
can you explain that more to us - as that was NOT told to me when I put in the fix.
support just said - add this it will fix the issue.
dynamox
9 Legend
•
20.4K Posts
0
June 2nd, 2014 13:00
btw i am on 7 and vSphere 5.5 and i am occasionally getting these.
GNeal11
1 Rookie
•
21 Posts
0
June 2nd, 2014 13:00
I'm running vCenter 5.5 and Avamar 7.0.
The command added in fixed it. I had to add a similar line for another error code - 10056. Avamar supplied great info on that error, not sure why they didn't give better info on this one!
I'll add this line to the dataset w/ the other and tonight will be a good test if it works for the other 1/2 dozen that were getting this error.