Unsolved
This post is more than 5 years old
1 Message
0
3222
September 5th, 2013 07:00
code2: Error while backing up client in avamar
Hi,
Good Day,
Can someone help me understand the reason why I am getting the following error while backing up the files in a client through Avamar version 6.1.101-87/Server Windows 2003 R2 SP2?
I am getting the same error since past three days. Although I am able to do on-demand backup successfully but the scheduled backup is failing for same directory but different files.There are no new patches installed in the server in near past that can be of concern and there are no VSS writer issues either. Also there are no volsnap errors reported in eventlog.
avtar Error <5137>: Unable to open "******" for backup (code 2: The system cannot find the file specified)
. (Log #1)
avtar Error <5244>: Unable to open directory "*****" (code 2: The system cannot find the file specified). (Log #1)
Thanks in advance
rpervan
266 Posts
0
September 5th, 2013 08:00
it looks like a file is not snapped up since we are unable to open file ...
Can you confirm that your Win2003 have applied hotfix referenced in KB833167 ?
http://support.microsoft.com/kb/833167
J_H_
2 Intern
•
498 Posts
0
September 5th, 2013 12:00
same files every day or different files/folders every day? is it by chance a users dir for folders like mydocuments?
DELL-Leo
Community Manager
•
9K Posts
0
September 5th, 2013 18:00
Hey,
It is a known issue. It is a Microsoft bug, see their hotfix referenced in KB833167.
The soluton number is esg94299.
Solution link: https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000fOG
If you cannot open the solution link, please tell me, I will send out to you.
Doobster
3 Posts
0
April 21st, 2016 08:00
I cannot access this page and I have the same error 5137
ionthegeek
2 Intern
•
2K Posts
0
April 21st, 2016 12:00
This normally happens if the volume on which the VSS snapshots are stored does not have enough capacity available to maintain the snapshot, resulting in its deletion mid-backup. I'd recommend that you review the system and application event logs for VSS or volsnap messages. You may need to increase the amount of storage allocated for VSS snapshots or relocate the snapshot storage to another volume.