Files Skipped: Updates.log and upd.lock via backup exec 2010 and EV9

[Chris242]

Hi all, I'm getting the follow warning messages every backup.

Warning: Unable to open "E:\Index\Index1\index8\1BBA5BB93B1DD944B93708445ACC0C2481110000ocwev01\upd.lock" - skipped.

Reason: The process cannot access the file because it is being used by another process.

Warning: Unable to open "E:\Index\Index1\index8\1BBA5BB93B1DD944B93708445ACC0C2481110000ocwev01\updates.log" - skipped.

Reason: The process cannot access the file because it is being used by another process

I found this thread that has the exact same problem, but I don't know what task to adjust in order to resolve this.  Any insight would be great.

https://www-secure.symantec.com/connect/forums/ev-backup-error-log-process-cannot-access-file-becaus...

[TonySterling]

Okay, so have you tried to run the powershell on the EV server itself? Not using the BE Agent.

[Chris242]

Yes, if I run the powershell scripts I posted up the thread, it goes in and out of backup mode just fine.

[TonySterling]

So what account is running the script in BE?

[Chris242]

The EVAdmin account.  The same one as I run it as when I log in.

[Chris242]

Event viewer makes it look like it's working when the EV Agent for BE handles it.

-First Event

Disabling additions, deletions, and updates because the index location is in backup mode. 

Index Location: E:\EVStorage\Index\index6 

Status: Success  [0] 

-Seconds Event

Enabling additions, deletions, and updates because the index location is no longer in backup mode. 

Index Location: E:\EVStorage\Index\index6 

Status: Success  [0] 

[TonySterling]

Ok, is there any thing wrong with that index?  Is it failed or have missing items?

[Chris242]

1.How do I check?  

2.Should I rebuild it?

[Chris242]

See attached

[TonySterling]

Did you look at the right one?

In your original post you have this:

"E:\Index\Index1\index8\1BBA5BB93B1DD944B93708445ACC0C2481110000ocwev01\upd.lock"

but then later you have:

E$\EVStorage\Index\index6\1653716244DBE524BB23FB8BC75A0DC011110000EVAULT1.CORP.US-GF.COM\updates.log

[Chris242]

E$\EVStorage\Index\index6\1653716244DBE524BB23FB8BC75A0DC011110000EVAULT1.CORP.US-GF.COM\updates.log ---  is the right one

I posted the wrong one at first.  My bad.

[TonySterling]

are other index locations put into backup mode ok?

You might need to open a case to have support take a look for you. 

[Chris242]

yep, everything else appears to be fine.  I may do that later on tonight.

[Chris242]

I opened a case: 413-066-093.

2 hour call back.

I will post with updates.

[TonySterling]

Cool, I am interested to hear the outcome!

[Chris242]

Tony, still waiting on the call back, but do you think this has anything to do with me not being on R2 of BE 2010?

[Chris242]

Looks like it is the indexserver.exe locking the file.  We are trying to figure out why.

[Chris242]

Tech said it sounds more like a BE issue.  I got a new case number for BE: 413-073372

On hold now to talk to someone about this case.

Will post back with updates.

[Chris242]

Rob, I talked with a BE guy and he said this was a known issue with EV Agent.

He said to refer to this internally.  etrack: 1637909

Let me know if you have any new thoughts.

[Chris242 · Accepted solution]

Upgraded to Backup Exec 2010 R2, deployed the new agents to the clients, and upgraded my FSA client from 8.0.4 to 9.  Now it all works.

[TonySterling]

Hey Chris,  Thanks for sharing the solution!

Regards,