Backup exec error: Access denied to directory

[SymQNA]

We are running backup exec and backup agent with administrator account which has permission on all folders.

MMS server: backup exec 2010 R2
backup agent: Unix server RedHat 5

We have tried KB http://www.symantec.com/business/support/index?page=content&id=TECH38357&actp=search&viewlocale=en_U... but does not work.

backup error

  Access denied to directory var/named/chroot/procduction/12345/task/12345/fdinfo/. http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-57344-33928

- Access is denied. Access denied to directory var/named/chroot/procduction/12345/task/12345/fd/. http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-57344-33928

[pkh]

What is the exact version of RHEL that you are using?  Like 5.4, etc.

Are you using root as the backup credential?

[SymQNA]

Distributor ID: RedHatEnterpriseServer
Description:    Red Hat Enterprise Linux Server release 5.7 (Tikanga)
  yes, using root as backup credential
  most of data can be backed up, but failed for /.

[pkh]

I would suggest that you upgrade to BE 2010 R3 which is the latest version. Your existing licence keys will work.  You can download BE 2010 R3 from either the fileconnect site or

http://trialware.norton.com/files/fc/Backup_Exec_2010_13.0.5204_MultiPlatforms_Multilingual_DVD.iso

After your upgrade, do not forget to run LiveUpdate a couple of time to update it to SP3 and the latest hotfixes.

After you have upgraded to R3 Sp3, push out the remote agent again.

=============

Are you using the 3.0 kernel?  If so, it is not supported.  BE only support the 2.6 kernel.

[SymQNA]

Hi Symantec support

Have you ever encountered same issue before and fixed it by upgrade? We prefer to have other solution besides upgrade. Can you please advise?

[Jaydeep_S]

Not sure whay you are getting an access denied. It is better if you open a support case to work on the issue as a debug might show some additional errors which may help fix the issue.

Having said this, if there is some error that is discovered in the debug that might requirte a fix, BE 2010 R3 with SP3 is the current version based on which a fix can be created if required.