Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

backup exec 2012 credentials problem

Created: 01 Aug 2013 | 5 comments

HI,

I have a backup exec 2012 server on windows 2003, both upgraded. But I have credentials problems with the BESA.
The test with credentials was been failed but I think that all permissions are ok.

The following is what I've done.

It is member of the folloing AD groups:

  • administrators
  • domain admins
  • backup operators
  • domain users
  • Exchange Organizations Administrators
  • Exchange View-only administrators

Also it has the folloing gpo

  • Act as part of the operating system
  • Backup files and directories
  • Create a token object
  • Logon as a service
  • Manage auditing and security log
  • Restore files and directories
  • Take ownership of files and other objects

and,finally, all the be service run as BESA.

What  I miss ?

Operating Systems:

Comments 5 CommentsJump to latest comment

Donald Eady's picture

Im a bit confused at what it is that you mean by all services are running as BESA... some services should be running as Domain\Admin and some should be run as System Logon... Please view the document below and verify that your services are running as such 

 http://www.symantec.com/docs/TECH195898

I hope this posting was helpful

  

bellissimopython's picture

HI, I changed the services rights into that are explained in the link.

but, nothing was changed.

Donald Eady's picture

after doing so did you restart backup exec services?? if not please do so 

I hope this posting was helpful

  

Kunal.Mudliyar's picture

It could be cosmetic. Can you run the actual job?

Does it fail with credentials error?

Technical Support

Symantec

MusSeth's picture

Hello,

as kunal mentioned this could be a cosmetic issue, please check the technote below, this could be a known issue mentioned in the technote http://www.symantec.com/docs/TECH197149

please try running a backup if that works, than you can subscribe this article, you will notified about the same once it is fixed.