Troubleshoot an issue with the Backup Exec Service Account locking out during a backup operation.

Article:TECH164437  |  Created: 2011-07-12  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH164437
Article Type
Technical Solution

Issue



Troubleshoot an issue with the Backup Exec Service Account (BESA) locking out during a backup operation.


Error



Active Directory logon account is locked out.


Solution



The Backup Exec service account locking out has several possible causes. Here are a few possible solutions:

1) The account used in the backup job is using an incorrect password. To correct this, open the Backup Exec console and select Network > Logon Accounts.... Select the account used for the backup and Edit.... Select Change Password... to update the Backup Exec account to the proper password.
2) The Backup Exec services are using an outdated password. Open the Backup Exec console and select Tools > Backup Exec Services... > Services Credentials.... Check the top box to "Change service account information and provide the new logon account information. Select OK, then restart the Backup Exec services.
3) The Active Directory account has issues with the amount of resources it was used to logon to. Change the BESA and System Logon Account to another domain administrator in another Active Directory Organizational Unit (OU). Open the Backup Exec console and go to Network > Logon Accounts..., change the "System Logon Account" to the other administrator. Then from the Backup Exec console again, go to Tools > Backup Exec Services > Services Credentials and change the user account to the other domain administrator.
4) A third party product is trying to logon to domain resources using old or incorrect credentials at the time of the backup job. To determine if this is the case, stop the Backup Exec services during a typical time period when the logon account is locked out. If the logon account is locked out still, there is a 3rd party product locking out the account.




Article URL http://www.symantec.com/docs/TECH164437


Terms of use for this information are found in Legal Notices