11-16-2010 02:10 PM
I have been able to backup VMWare virtual machines successfully under Backup Exec 2010. I installed BE 2010 R2, and now when attempting to backup the VMs, I receive this message:
"0xe0009b61 - The logon account that was provided does not have valid credentials. Ensure that the user name and password are correct, and then try again."
Another server with the same BE version is able to backup the VMs without a problem. Any idea how to resolve this?
Solved! Go to Solution.
11-18-2010 11:30 AM
I figured this out. In Backup Exec under Logon Accounts on the problematic server, I deleted the "root" account that was used to login to VMWare. I then transferred "root" from BE on a successfully backing up server. The backups are now able to run with this transferred account.
Note that I had deleted and recreated the root account on the problem server, but this did not correct the problem. Something with the transferred account was different enough to allow the backup to occur.
11-16-2010 07:57 PM
In the backup job you have added the virtual center or the Esx server name?
After upgrading to r2 did you change the credentials or anything that might be causing this.
In the job itself when you check the credentials what does it say.
11-16-2010 08:16 PM
11-17-2010 06:41 AM
In answer to the two responses, the credentials are correct. When selecting the virtual server for the backup, I choose the logon account of "root", and it is accepted. This account worked prior to the upgrade, and the password has not changed. I have removed then readded the account to Backup Exec, but this had no effect.
Also, the server is only selected under "VMWare vCenter and ESX Servers", and not under the domain.
11-18-2010 10:15 AM
I can backup virtual servers and the credentials are read fine on two media servers, but fail with two other media servers. The servers that can get a backup are both running on top of ESXi. The failing servers are not virtualized.
That's the only difference I can see right now. All are running BE version 2010 R2. All are configured the same under the VMWare agent section.
One difference that could have an impact is that the successful servers are either installed new with BE 2010 R2 or upgraded to it from BE 2010. The failing servers started out at BE 12 if not earlier. Maybe some component of BE fails when upgraded versus being installed new. I could do a complete uninstallation then reinstallation, but that is serious surgery on our servers.
Still happy to hear suggestions for getting this working.
11-18-2010 11:30 AM
I figured this out. In Backup Exec under Logon Accounts on the problematic server, I deleted the "root" account that was used to login to VMWare. I then transferred "root" from BE on a successfully backing up server. The backups are now able to run with this transferred account.
Note that I had deleted and recreated the root account on the problem server, but this did not correct the problem. Something with the transferred account was different enough to allow the backup to occur.