Unsolved
This post is more than 5 years old
31 Posts
0
3587
April 6th, 2012 05:00
Error 5139 within Windows 2008 VSS Backup
I have a Windows 2008 R2 server that I am doing both Windows File System and VSS backups on. This server runs Symantec EndPoint Protection software and both Windows File System and VSS job are completing with excetpions. There are about 45 Symantec EndPoint Protection files that are failing with the following.
avtar Error <5139>: File access error "c:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Logs\tralog.log" (code 32: The process cannot access the file because it is being used by another process).
As this is a low priority server and the rest of the data on this server is be backed up succesfully, we were hoping to just exclude the "c:\ProgramData\Symantec\Symantec Endpoint Protection" directory from the Dataset. In doing so the Windows File System backups now complete succesfully, but the VSS jobs still completes with exceptions. Since you cannot specifiy exclusions that are applicable to the VSS plugin, what would be next steps, whether in configuration or troubleshooting, to rectify these errors.
Ken
Bebo2k
544 Posts
0
April 6th, 2012 05:00
Hi Ken,
Please check this community thread regarding the same issue:
https://community.emc.com/thread/131483
Hope it helps you.
Thanks,
Ahmed Bahaa
kclebak
31 Posts
0
April 9th, 2012 05:00
While this thread did provide a lot of good information, and it did state that this could be related to Windows Junction Points that has known issues with better support coming in Avamar 6.1, I still have one question that I would like to see if I could get answered.
Should I be received file access errors when conducting a VSS backup? I can understand the issue in conducting a Windows File System backup, but I would the a VSS backup would be handled differently.
Could I get confirmation that the stated Junction Point issues are the same regardless of peforming a Windows File System or VSS backup? If so, we can just table this issue an wait for 6.1.
Thank You
ionthegeek
2 Intern
•
2K Posts
0
April 9th, 2012 07:00
VSS backups should really be called VSS System State backups. Both regular file system backups and VSS System State backups use VSS to take a snapshot, then back up that snapshot using the regular file system client. The VSS System State plugin does additional work to capture the system state and record it in the backup (and the file system backups is used to back up any non-critical volumes, i.e. your data volumes) but the mechanics of actually backing up a file system are the same regardless of whether that file system is being backed up by the VSS System State plugin or a regular file system backup.
tl;dr: The junction point issues affect both VSS and file system backups.