Jump to content

Recommended Posts

Posted

I have had a few consecutive backup failures on my admin network using Veritas 10 with error:

e00084af - The directory or file was not found, or could not be accessed.
The log then directs to a link that suggests Five or so solutions which only Two are relevant. One was to exclude the DO_NOT_REMOVE_NtFrs_PreInstall_Directory from the selection but this has made no difference. The other was related to the Advanced Open File Option which i have disabled anyway so don't know what's causing this to fail.

 

I'm currently running this manually and again have recieved a failed notification saying

The job failed with the following error: The directory or file was not found, or could not be accessed.

 

Any ideas?

Posted
Its not trying to backup something off another server and the password used to access that server has changed ? I know we had a similar message when we changed our admin password, and forgot to alter the password on Veritas used to access the other servers
Posted

There is nobody logged on when the backup runs. I have a scheduled forced shutdown in place to ensure this.

 

There isn't any remote backup taking place, just local on the server

Posted
I have Sophos 6.5.3 client but this has never been an issue in the past. Scans take place during the day. Backup happens 22:00
Posted
It's just dawned on me that this started failing just after i installed SP2 for 2003. This almost certainly looks to be the problem but i still don't know why or what i can do
Posted

Have you moved this directory onto another server recently? If this is the case and you haven't re-designed your backup, veritas will be looking for a directory that simply doesn't exist.

 

Also, does this error prevent you from performing a restore?

Posted

@kearton: No i haven't......I have now and has made no difference :¬(

 

@bandgeekmafia78: There have been no changes made to location since this started failing.

 

I haven't tried a restore but i think my next move is to re-install veritas BE

Posted
it could be that the drive is knackered. i've had instances in the past where this has been the problem and veritas has given seemingly non-related errors. that was on autoloader units though... and yours is a single unit isn't it?
Posted

The drive is about 1 year old and i'm certain this insn't the problem.

 

I have tried a B2D job and this also fails with the same error so this looks to be software

Posted
Apparently this is a known issue between BE 10.0 and Win Svr 2003 SP2. Capita gave me v10d and it now works fine. Weird how i never saw this issue when googling this!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...