Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

BE2010 R2: "Directory does not exist"

Created: 13 May 2011 | 4 comments
MIXIT's picture
0 0 Votes
Login to vote

This is an ongoing problem with a few other thrads having been created in the past, but for all intents and purposes it's best that I just start a new one. 

To summarize:

Single 2003 R2 server, single RAID 1 array, DAT72 (nternal) for backups.  Was using ntbackup for 3+ years, and getting the same errors with that but recently installed BE2010 R2 (Trial but fully functional).  the AOFO option was installed and it is turned On in the Tools > Options menu of BE. 

Getting the following error during a backup:

V-79-57344-65033 - Directory not found. Cannot backup directory \DATA and its subdirectories.
 

This error occurs for most of the folders on this volume but I just copied and pasted the most significant one since this \DATA folder houses almost all the company data (user files, database files, etc). 

Following is the artcile that the V-79-57344-65033 link points to in the error text of the job log.  There are limited suggestions in there but the one I haven't ried yet is to disable the antivirus (SEP 12.0 SBE), so I've just disabled that and am running a backup job now.  Here's the article:  

http://www.symantec.com/business/support/index?page=content&id=TECH71493

Does anybody have experience with dealing with this error?  could it be a file system problem?  I had run a chkdsk not long ago and it hadn't found any problems...and this \DATA folder along with all the other ones that the job log ferences as non-existent, do in fact exist. 

I'll post results from the backup job with antivrus disabled. 

Comments

Ken Putnam's picture
13
May
2011
0 Votes 0
Login to vote

RE: BE2010 R2: "Directory does not exist"

Verify that the BESA is in the local Admins group, or that Admins have not had rights removed from that/those directories

If this response answers your concern, please mark it as a "solution"

MIXIT's picture
13
May
2011
0 Votes 0
Login to vote

BESA?

Verified that local admin group (this is a non-domain server) has full control over all those folders.  About the BESA, is that "SA = service account"? I checked the Log On tab for the 7 BE services - about half of them specify ./Administrator, and the other half are just set to "This account", which is also the same Administrator that I'm logged in with.  In Local users & Groups via Computer Management, there are no Symantec-related accounts of any kind so I must assume you meant the Logon As tab.  Please let me know, thanks! 

Ken Putnam's picture
14
May
2011
0 Votes 0
Login to vote

RE: BESA?

BESA = Backup Exec System Account - The account that the BE services run as.  Normally it is a separate named account that is a member of Domain Admins (or local Admin in a non-Domain environment)

 

Hmm

 

If you logon to the media server as the BESA, can you access that/those directories??

If this response answers your concern, please mark it as a "solution"

MIXIT's picture
14
May
2011
0 Votes 0
Login to vote

No BESA

I double-checked...there's no account at all in Local users & Groups...I've got the standard Administrator and then just a handful of users.  The BE services are all effectively being run as Administrator (local since this is a workgroup), just that some are explicit (Logon As = ./Administrator), other ones have the radio button for "This Account" selected, which is the Administrator that i'm logged in with. 

Should there be a BESA account created somehow?  It didn't occur automatically, perhaps I should have made one?  There was no indication in the installatino process though.