cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec backup VMware job fail with credential error

linhnm
Level 3

Hi all,

I've got a abnormal error with Backup Exec 16 (with VRAY license) when try to backup a VM through my vcenter server. We're running vcenter 6.5 and 3 ESXi 6.5 enterprise plus

I added my vcenter, browse VM which needed to backup then run the job, but it fail with error: 0xe0009b61 - Backup Exec could not log on to the server with the logon account specified for it. The logon account does not have valid credentials. Ensure that the user name and password are correct in the logon account.

Our Backup Exec server and vcenter, esxi hosts are in the same network, no firewall turn on, BE agent for VM is not installed and I'm using vcenter admin account: administrator@vsphere.local

It is such an easy task and should be work smoothly. I have some work around but currently still have no idea about the problem. Any suggestion? BE engine log is attached.

Thank you

1 ACCEPTED SOLUTION

Accepted Solutions

Those lines from the debug are normal.

Looking at the debug you attached earlier, that failure is on the connection to the local host.  Since we make a loopback connection to the remote agent before connecting to the ESX host it's failing on connecting to itself.

Do you still have a system logon account listed in Backup Exec?

Configurations and Settings - Logon Accounts - Manage Logon Accounts

View solution in original post

7 REPLIES 7

Gurvinder
Moderator
Moderator
Employee Accredited Certified

[4064] 2018-05-19T13:55:46.982 [ndmp\ndmpclient]    - connectClientAuth(): agent is on local loopback, skipping SSL connection...
[4064] 2018-05-19T13:55:47.310 [ndmp\ndmpcomm]      - ERROR: 69 Error: Windows LogonUser API failed.
[4064] 2018-05-19T13:55:47.310 [ndmp\ndmpclient]    - connectClientAuth(): agent is on local loopback, skipping SSL connection...
[4064] 2018-05-19T13:55:53.362 [ndmp\ndmpcomm]      - ERROR: 69 Error: Windows LogonUser API failed.
[4064] 2018-05-19T13:55:53.362 [ndmp\ndmpclient]    - *** getLastNDMPError Calling to get last NDMP Error.
[4064] 2018-05-19T13:55:53.362 [loops]              - NDMPRAHostBackupEngine::ConnectToDataServer() failed. Error = 0xE0009B61.

there should also be an always on beremote log from the same time

https://www.veritas.com/support/en_US/article.100024594    see if this helps

 

I tried that link, but no worked. This backup task require only some very simple configuration, but somehow it fail

Update: I tried debug to see anywrong by SGMON, and now I can see this:
176 BESERVER 5224 5/21/2018 9:51:40 PM 6456 "Cluster" key is not present in the registry
177 BESERVER 5224 5/21/2018 9:51:40 PM 6456 Did not detect Microsoft cluster ()
178 BESERVER 5224 5/21/2018 9:51:40 PM 6456 VCS cluster keys do not appear to be present in the registry
179 BESERVER 5224 5/21/2018 9:51:40 PM 6456 Did not detect VCS cluster ()
Will reinstall help?

Those lines from the debug are normal.

Looking at the debug you attached earlier, that failure is on the connection to the local host.  Since we make a loopback connection to the remote agent before connecting to the ESX host it's failing on connecting to itself.

Do you still have a system logon account listed in Backup Exec?

Configurations and Settings - Logon Accounts - Manage Logon Accounts

Hi Ben, I think your idea is a very remarkable. Backup Exec was installed and used admin domain account as system logon account. Now admin domain password is changed, and I don't have the old one, cannot edit system logon account. I will check more about this, but it would be greate if you guys could show me some useful article. Thank all

Hi Ben,

I re-created system logon account, and it worked like a charm. Thanks very much. You are the best.