Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1155
  • Last Modified:

DSA signature is not getting updated on the Domain Controller

DC - Windows 2003 SP2
Backup Exec 11d runs on a Windows 2003 SP2

When I do a full backup of my DCs; (C drive, Utility partition, System State, Shadow Copy Components); the DSA signature is not getting updated by Backup Exec. I get the event ID 2089: "This directory partition has not been backed up since at least the following number of days".  Now, I do see all the pertinent information with regards the being able to backup & restore the DC and active directory within Backup Exec itself.

Here is the kicker ... When I do a backup of only the System State -  the DSA Signature is "updated" and all is well.

I do not want to have to have seperate jobs to run for the system state, HELP?!
0
RussTre
Asked:
RussTre
  • 2
1 Solution
 
Mike KlineCommented:
There was also a thread about this over on the symantec forums  http://www.symantec.com/connect/forums/11-d-system-state-backup

It looks like Backup Exec may not be using the proper method to update it during that full backup.  I wish someone from Symantec could have verified that.  I'm not 100% sure.

 Probably safe to ignore if the backups are successful but I'll keep looking around.

Thanks

Mike
0
 
RussTreAuthor Commented:
I got it firgured out. Besides Domain admins and backup operators, the backup exec account needs to be part of these 'policies' under local policy > user rights assignment

•Act as part of the operating system
•Create a token object (which can be used to access any local resources)
•Log on as a service
•Log on as a batch job (allows a user to be logged on by means of a batch-queue facility)
•Backup files and directories (provides rights to backup files and directories)
•Restore files and directories (provides rights to restore files and directories)
•Manage auditing and security log
•Take ownership of files and other objects

After they are in them (if not add the account); at a command prompt run gpupdate /force

This fixed it for me.
0
 
RussTreAuthor Commented:
This is what fixed it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now