Video Screencast Help

Backup failing. "Process cannot access the file because another process has locked a portion of the file"

Created: 04 Dec 2012 | 6 comments

I have one PC that fails it's backup every now and then with this particular error:

Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file.

This PC is backing up to an external drive, G:, and it runs successfully some of the times. Here's the latest series of entries in the Backup Exec System Recovery.log file:

 

12/3/2012 23:00:10 PM High Priority Info: Info 6C8F1F65: The drive-based backup job, * - Backup to G:, has been started automatically. 0x00 (Backup Exec System Recovery)
12/4/2012 0:47:38 AM High Priority Warning:  0x800706BA (Backup Exec System Recovery)
12/4/2012 0:47:38 AM High Priority Error: Error EC8F17B7: Cannot create recovery points for job: * - Backup to G:. Error E7D1001F: Unable to write to file.
 Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file. 0xE7D1001F (Backup Exec System Recovery)
 (UMI:V-281-3215-6071)

 

I cannot figure out what is locking the file and I don't know what file is actually locked. I've been using a program called Processlock:

(http://windowsxp.mvps.org/processlock.htm) to try to figure out what has the file locked, but I need to provide the exact file name in order to do so.  I've found a few Symantec knowledge base documents about this error, but they always reference backing up to a network share/admin share as the issue and this isn't the case here as this is a local external drive. Is there anywhere where I can find more detailed logging to see what file actually is being locked and therefore cannot be accessed? Thanks

Comments 6 CommentsJump to latest comment

Backup_Exec's picture

Hi

We do not do a file level backup using SSR but do a sector level backup using SSR
It will not be possible to tell from the SSR console as to which file is being locked
The snapshot process happens towards the start of the backup job and over here the failure is happening towards the end after the job runs for about 6 hours
So the issue is ideally related to the backup files that BESR is genrating at the destination and somehow the file is getting locked

Additionally you have not mention what version of BESR or SSR is this and first thing I will do is ensure it is fuily patched with latest updates.
 

http://www.symantec.com/docs/TECH55684

http://www.symantec.com/docs/TECH125517

http://www.symantec.com/docs/TECH158113

http://www.symantec.com/docs/TECH57808

http://www.symantec.com/docs/TECH124774

 

Thanks

 

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

Jon Sumida's picture

This is for BESR 2010. Latest updates.

 

Thanks for the links. None of those really apply to my situation. The only error message I get is the one I posted before and it only happens with one PC. I have around 100 other PCs installed with same version and using the same backup policy. This is the only one. I have a feeling it's another piece of software that is doing scanning or something. I just wanted to see if there was a way I could narrow it down to figure out what that process was.

Backup_Exec's picture

Hi

You would like to verify which porcess it was then use process monitor and then click on search in that and enter the file name and it will list the porcess name it has lock on it

 

Hope that helps

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

Jon Sumida's picture

That's why I'm asking. In order to see what process is causing Symantec to not have access to the file it needs, I need to know what file is being accessed. You say to use process monitor and enter the file name. What file name? The .sv2i file? One of the image files? I have process monitor running right now and don't know what to search for.

TRaj's picture

What OS are  you using? Also is it any database like SQL or Exchange?

How many drives are you backing up ? Also at what % do you receive the error message?

Do you have BE or any other snapshot running while you take the SSR backups? ( what is the schedule? )

Do you have "Perform Full VSS" option enabled?

I will request you to run a local backup on the same disk and check if the issue occurs. Like run a C: backup on the D:

We are requesting you to mark the forums as Solution , so that is makes easier for the viewer to search and refer the posts with "Solutions"

Jon Sumida's picture

OS is Windows XP Professional. No database. Just a desktop backing up 1 drive to an external drive. The % it fails at varies. I have the PC set to backup at 11PM daily. At some point through the backup process, it will fail. The odd thing is that sometimes it will work. That is why I was hoping to find in some logs exactly what "file" it's failing on when the error message states:

Notification Type: Error

Priority: High

Description: Error EC8F17B7: Cannot create recovery points for job: * - Backup to G:.

      Error E7D1001F: Unable to write to file.

            Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file.

Details: 0xE7D1001F

 

It says the process cannot access "the file". I would like to know what that file is. This will help me be able to better track down the other process that is locking it.

I do not have "Perform full VSS backup" checked.

This technically is a local backup.  Backing up C: to external drive F: