Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Final error: 0xe00084af - The directory or file was not found, or could not be accessed when backing up Linux Home areas on Server 2k3 machine

Updated: 21 May 2010 | 4 comments
ITGroupTel's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hello

We have recently started having problems backing up Linux Home areas on a Windows Server 2003 machine running Backup Exec 12.5 SP2.
The following errors are:
Backup- E:
Directory E:\Shared.Folders\Home\xxxxx\ was not found, or could not be accessed.
None of the files or subdirectories contained within will be backed up.

This had been working fine and nothing appears to have changed.
I have checked folders and can access them ok and browse through them using the selection option in Backup Exec.

I hope someone can help

Many thanks

Comments

CraigV's picture
06
Nov
2009
2 Votes +2
Login to vote

Hi dude, I'd start by

Hi dude,

I'd start by deleting your selection list and recreating another one.
Could be some corruption with it.

Laters!

If you find this is a solution, please mark it as such.

ITGroupTel's picture
06
Nov
2009
0 Votes 0
Login to vote

That was the first thing that

That was the first thing that i tried and had no effect.
But thanks anyway

ITGroupTel's picture
24
Nov
2009
2 Votes +2
Login to vote

SP3

I installed SP3 and this seems to have solved the problem

Wolfi3's picture
07
Apr
2010
1 Vote -1
Login to vote

Hi Not sure if this is

Hi

Not sure if this is related to you?
But I have the same error when backing up to Disk.
Whene backing up the information store I get the following error message with the 0xe00084af:
"Database  was not found, or could not be accessed"
Just found that there is a fix for my problem. Not sure if it is related to yours?

Still need to test out this hotfix to see if it works.
http://seer.entsupport.symantec.com/docs/319932.htm

If not, they say there is a work arround.
http://seer.entsupport.symantec.com/docs/305877.htm