I wish I could say that the client agent and/or the job engine logon solved my "sharing violation" situation.
Here is what I have:
ARCServe 2000 SP3 running on W2k SP2 that is backing up three other W2K SP3 servers.
I have created a backup account called "backup" in the domain. Backup has Domain Admin and Backup Operator rights throughout the domaina as well as local admin rights on the servers. Backup operator logs on as a service and part othe the OS for the advanced rights.
I also have Backup Agent For Open Files configured to run on the servers and the console on the backup server.
I use two Compaq TL891 DLT libraries, with the latest firmware.
When the backup agent is running on the machines, logged on as a local service I get the sharing violations. When I serch the tapes through the restore by session and expand the trees, the JPEG files in question are backed up. Also on the BAOF logs....it states that the file was open and closed. I am not sure what that is telling me. I think that is means the Open File agent kicked in for those files listed. When BAOF is not running the files are not on the tape, and I get the same errors.
If I run the Job engine as local serive and not the domain backup the problem is still there. This leads me to beleive that the log on as a domain backup for the Job engine is not the solution, at least for me.
The client agent is really interesting...Under the ARCserve manager job logs, the sharing violations are not there. But when I read the line "Total Skips" I get a number that corresponds to a list of sharing violations that are listed in a separte log file on the other backup server that is running the client agent. For exmaple for Server A I get 15 skips. Located under the Computer Associates folder Client Agent logs there is a list of 15 files (JPEGS) where there is "Unable to Read File" which is the same as the "sharing violations."
So, the sum this rant and rave up, I noticed that the client agent removes the errors from the job lists, but relocates them to a log file on the server that is being backed up. At first I thought the client agent fixes the problem, but for me it just makes the errors harder to find.
I still have an open ticket with Tech Support about this and they are usesless. Besides having to force the guy to repeat every sentence due to his poor English, I do not feel that CA can fix this problem. If anyone else is having this problem I feel your pain. I am willing to try any other suggestions and will greatly appreciate them.
Nick