jtcomstock
asked on
Backup Exec 10d and Microsoft SQL
I'm having challenges with BackupExec 10d in trying to backup four databases. I get "Authentication failed on connection to server..." when I test in the resource creditentials screen. I'm using an account that is in the domain admin group and get successful with other parts of the backup job.
I'm running on SBS2003 and this job was working correctly the first couple of days after setting up BE. I've looked through the BE configuration and don't see any obivious changes.
I would appreciate a suggestion on how to get authentication working for the SQL databases on this system.
Thanks,
Jason
I'm running on SBS2003 and this job was working correctly the first couple of days after setting up BE. I've looked through the BE configuration and don't see any obivious changes.
I would appreciate a suggestion on how to get authentication working for the SQL databases on this system.
Thanks,
Jason
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I looked over the backup account I'm using and it was not part of the Backup Operators group, I changed that. I then went into the Domain Controller Security Policy (SBS2003), then to Local Policy, then User Rights Assignments, then Backup Files and Directors. Backup Operators was listed and I added the account to the list. After applying I did a gpupdate /force and had no change when I test the resource credentials.
I then change the account to use on one of the SQL instances, there are four, to the system logon account, no luck. Still getting the authentication failure.
What next?
I then change the account to use on one of the SQL instances, there are four, to the system logon account, no luck. Still getting the authentication failure.
What next?
ASKER
I built a new job and everything is working fine. Not sure what happened.
Jason
Jason
ASKER