Failed to Open File -or- File Does Not Exist

[monkeylizard]

AS 6.61 SP2a running on NT4.0 SP6a

I have a backup job that gives me the following errors.

AE0004 Failed to open file <C:\WINNT40\JETAB54.tmp>. RC=32, The process cannot access the file because it is being used by another process.

AE0005 Directory E:\BUILDFAST\DATA does not exist.


Error 1 (AE0004) only shows up for some TEMP files that I don't really care about backing up or not. Strange that I get this error though. I am running the OFA software. I can get rid of this message in my logs by de-selecting these files, but in a few days/weeks, different files give this same error and I have to de-select them.

Error 2 (AE0005) is an accurate error, the D:\BUILDFAST\DATA directory doesn't exist. It was an old directory that has been removed. ArcServe, however, seems to still think that it exists. I can de-select this directory as well from the backups, but why doesn't ArcServe recognize that it's not there? It appears to be looking for file names from it's own database rather than from the NT Server itself. That's not good.

I've heard that I can simply select the entire drive instead of de-selecting certain directories/files, but that's not an option. I run SQL 7.0 w/ the SQL Agent. Selecting the entire drive backs up the database twice, once through the agent and again by getting the .mdb and .ldb files in a straight backup. This kills my tape space and lengthens the job time.

Any thoughts on how to get rid of these? Is there a way to have AS recreate its internal file list for this server? Monkeylizard
-Isaiah 35-

 

[glenna]

Modify your backup by reselecting your files.
Arcserve is too stupid to realize the file or folder is no longer there. It is trying to read your original backup configuration. Glenn A
&quot;Do not meddle in the affairs of dragons, for you are tasty and crunchy and good with ketchup.&quot;

 

[ARCserveGuru]

GlennA, I beg to differ and find it quite offensive that you refer to ARCserve as Stupid. You just don't understand, it is doing it for a reason.

Behold, ARCserve has the ability to do two types of backups. One is Dynamic and the other is a snap-shot backup. If the little green box is fully colored in, then everything below the tree will be backed up DYNAMICALLY, if you remove or add a directory then it will be detected! If it is a half green box then it is a snap shot, therefore if there was a directory selected when the job was created and it was then later removed, arcserve will keep looking for it! It is static!

anyway, that is in rebuttle to GlennA's comments. Monkey lizard, with the above information about snapshots and stuff, you may be able to reconfigure the job which is getting the AW0005 errors so that they wont occur anymore. The problem with the open files (files being used by another process) is mainly due to the timeout threshold set on the open file agent, however this may not be the cause either? have you tried running through the job using the backup option &quot;Use lock mode if deny write fails&quot;. If not then try this. I think this will help you backup those nuisance files that are causing the problems. If not then we may have to look at editing the open file agent threshold.

good luck,

guru

 

[glenna]

My comments about Arcserve's Stupidy was based on information I got from CA Tech. Obviously, they gave ME wrong information. Glenn A
&quot;Do not meddle in the affairs of dragons, for you are tasty and crunchy and good with ketchup.&quot;

 

[monkeylizard]

Hmmmm....
Tech Support Strikes Again!

Thanks guru. I'll give it a try and post back here with the results. Monkeylizard
-Isaiah 35-

 

[ARCserveGuru]

Glenn A,
wherever you go mate, level one tech support will always be just that..... level 1. i.e. they know of the product nah thats harsh, but you know.....


guru