ARCServer 2000 issue, E00tmp.log 1

[Davetoo]

I've been arguing with my ArcServe 2000 backup for a while now, and so far it's winning.

I keep getting an error trying to backup \exchsrvr\mdbdata\E00tmp.log, RC=32, The process cannot access the file because it is being used by another process.

Ok, no big deal, so I add the file to the filter and exclude it. No joy, no matter what I try, it still gives me the same error every night. No other problems, just this one and it's annoyed me to the point of seeking help.

Any ideas?

TIA

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[fritz4000]

I am not sure if your ARCserve server is different then your Exchange server, try setting the filter by right clicking on the remote machine in the backup source screen. (I think that will set the filter for just that remote machine, it has been a while since I have used ARCserve 2000.)

 

[davidmichel]

If you use the Client Agent it should skip it by default.

 

[Davetoo]

The ARCserve is located on a separate server than my Exchange, and I am using the Exchange agent to back up.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[davidmichel]

Well of course you are.

The above message on backing up this log file is from a regular data backup and not the Exchange DB Agent backup.

So if the client agent is used to do the backup of the regular data it should automaticly skip the Exchange files like this log that are always open.

 

[Davetoo]

So, since I'm using my Exchange Agent to backup my Exchange server, why is it trying to backup a file that #1, it should even be trying to backup and #2, a file that I've excluded in a filter?

You'll have to excuse me, but I'm failing to find the answer in your response.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[davidmichel]

Ok lets try it a different way.

Exchange DB Agent backups does not backup files, it backs up the contents of files.

So the DB Agnet session is not trying to backup that file, another session is. Another session that would have to be a "regular data" backup, and so the recommendation to use the Client Agent.

 

[Davetoo]

fritz4000 - That did it! Thank you! It's been a while since I've had to add to a filter, because when I did what you said there were other files already set on that remote machine to filter as well that I must have done years ago when I setup the system.

Thank you thank you thank you, that's been bugging me for a couple of weeks now, just hadn't had time to solve the issue.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[dholbrook]

Hey David M.

Does this also work for the SQL server files? I also get a lot of SQL related files on several different servers that are in use and will not back up. I wondered because the Arcserve runs on the system that also contains the SQl Server, so I am beginning to wonder if the SQL agent or the Exchange agent or the ARCServe agent is running the show.

Thanks,

David H.

 

[davidmichel]

The Client Agent when used with any of the DB Agents should automaticly skip that databases' open program files. So yes it works with SQL also.

Problem with the local filters is for some reason they were taken out of version 9.0.