10-29-2010 12:23 AM
Hi all, I'm getting the follow warning messages every backup.
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.
Solved! Go to Solution.
11-01-2010 01:34 PM
Okay, so have you tried to run the powershell on the EV server itself? Not using the BE Agent.
11-01-2010 01:36 PM
Yes, if I run the powershell scripts I posted up the thread, it goes in and out of backup mode just fine.
11-01-2010 01:42 PM
So what account is running the script in BE?
11-01-2010 01:43 PM
The EVAdmin account. The same one as I run it as when I log in.
11-01-2010 01:57 PM
11-01-2010 02:02 PM
Ok, is there any thing wrong with that index? Is it failed or have missing items?
11-01-2010 02:03 PM
1.How do I check?
2.Should I rebuild it?
11-01-2010 02:07 PM
See attached
11-01-2010 02:14 PM
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
11-01-2010 02:18 PM
E$\EVStorage\Index\index6\1653716244DBE524BB23FB8BC75A0DC011110000EVAULT1.CORP.US-GF.COM\updates.log --- is the right one
I posted the wrong one at first. My bad.
11-01-2010 05:37 PM
are other index locations put into backup mode ok?
You might need to open a case to have support take a look for you.
11-01-2010 05:47 PM
yep, everything else appears to be fine. I may do that later on tonight.
11-02-2010 06:44 AM
I opened a case: 413-066-093.
2 hour call back.
I will post with updates.
11-02-2010 06:54 AM
Cool, I am interested to hear the outcome!
11-02-2010 07:52 AM
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?
11-02-2010 12:08 PM
Looks like it is the indexserver.exe locking the file. We are trying to figure out why.
11-02-2010 01:58 PM
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.
11-02-2010 03:05 PM
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.
11-08-2010 08:18 AM
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.
11-08-2010 08:47 AM
Hey Chris, Thanks for sharing the solution!
Regards,