Forum Discussion

kev2's avatar
kev2
Level 3
8 years ago

Backup Exec 15 - How to delete/replace System Logon Account

Hi I have a series of jobs setup in Backup Exec and some of them randomly fail with credential errors on the target server. Without any changes these jobs sometimes work fine. Event Viewer on the ta...
15
2008) Not Applicable
2014
Backup Exec
credentials
logon
  • DarthBilly's avatar
    DarthBilly
    8 years ago

    First, check the Backup Exec service accounts. There should be 7+ services for Backup Exec. Reset those accounts if they are not right.

    Ok, there's more to resetting the logon accounts. It means also resettling everything. You can set the Backup Exec Database to a default never been used state, but again you would need to recreate all the jobs. There is no simple way to reset accounts besides this that I know of.

    This is the Technote for resetting Backup Exec. None of the data backed up will be lost, however, Backup Exec will not know it's there until you inventory and catalog it.

    https://www.veritas.com/support/en_US/article.TECH66780

    You may want to wait to see if anyone else chimes in with a better idea as well.

     

     

DarthBilly's avatar
DarthBilly
Level 5

Right, the accounts inside of BE are not connected to AD, but it does know who the ower is.

Log in as the user depicted in the Owner field in the Logon Account Management UI. Once logged in you should be able to manage all the accounts that is owned by that user.

If you are still having problems with this, then create a new account (not the system logon account). Give it a "Account" name that is descriptive. Go to the resource you are having issues with and open the properties go that resource. Click on Credential and set it. You can accutally leave the System logon account alone and just set the credentials for the resources you need this way.

kev2's avatar
kev2
Level 3
8 years ago

Thanks for the reply DarthBilly but I'm no further forward :(

 

I logged on to the machine as the Domain Admistrator and owner of the accounts (I wasn't before). This is one of the accounts where BE doesn't accept the current AD password.

In Logon Account Management I select the System Logon Account, click 'Replace', select the account (which is a Domain Admin) that I want to be the new SLA and get the error - 'Unable to replace old Logon Account with new. The server has received incorrect or invalid data.'

I try and delete a non-Sytem Logon Account and it says it cannot be deleted because the following users have selected it as their default logon account and one or more are currently logged on to the media server. This user account is not logged in on the Windows box and no services or jobs are running under this user account.

I have already got the different jobs running under a different account but I'm having random failures. Testing the credentials within the job's properties passes and there definitely is no reference to the accounts I'm looking to delete in the GUI.

The situation I'm facing is that I do not make any changes to credentials or configuration and randomly get errors with the failure message 'The logon account that was provided does not have valid credentials.Ensure that the user name and password are correct, and then try again.' but the next time the job will be successful with exactly the same configuration. I would expect this error to be permanent.

Without any proper evidence I am suspecting that the jobs are somehow reverting back to the Sytem Logon Account if there is any delay with the specified account credentials being returned as successful.

I do know that this BE installation was installed as an upgrade to a previous version of BE (I don't know which version) but I've already resolved issues with automated catalog jobs running that aren't supported with this version and issues with the catalogs being merged into its SQL database. I've also recreated the jons to no avail.

So, I'm left with Logon Accounts in BE with faulty credentials and would like a way of cleaning them up to see if it helps.

  • DarthBilly's avatar
    DarthBilly
    Level 5
    8 years ago

    First, check the Backup Exec service accounts. There should be 7+ services for Backup Exec. Reset those accounts if they are not right.

    Ok, there's more to resetting the logon accounts. It means also resettling everything. You can set the Backup Exec Database to a default never been used state, but again you would need to recreate all the jobs. There is no simple way to reset accounts besides this that I know of.

    This is the Technote for resetting Backup Exec. None of the data backed up will be lost, however, Backup Exec will not know it's there until you inventory and catalog it.

    https://www.veritas.com/support/en_US/article.TECH66780

    You may want to wait to see if anyone else chimes in with a better idea as well.

     

     

    • kev2's avatar
      kev2
      Level 3
      8 years ago

      Yip, backup exec services are correct, restarted lots of times, server restarted, all patches installed including updating the remote agents so I seem to have hit a dead end.

      I think I'll end up using the article you sent so thanks for that. I'll also take your advice and sit on my hands for a while before wading in ;) Now thatI've read the article it makes sense that I have to create a new DB but it's a shame BE doesn't integrate nicely with AD with regards to the logon accounts.

      But your input is greatly appreciated and thanks for the pointers.

      • Hopsnbarley's avatar
        Hopsnbarley
        Level 4
        8 years ago

        Perhaps you could attach a screenshot of the Logon Account Management screen (don't worry, it doesn't display passwords!). This should display the "account name" as well as the "user name".

        Just trying to clear up my confusion of what your seeing  :)