Based on the message about vCenter being logged directly in the avvcbimage log, I am assuming this is Avamar 6.1. If this is incorrect, please let me know.
This message means that when the proxy tried to log into the vCenter to take a snapshot, the login failed.
To try to narrow down the problem, please log into the proxy as root (default password: avam@r) and try to ping mavmbwvc. If this fails, the problem is likely with name resolution. Either the proxy does not have the correct DNS information or DNS is mis-configured.
If you can ping the vCenter, try running the following command:
If you're prompted for a username and password, type in the credentials for the vCenter user that Avamar will be using (the username appears to be vcenter_avamar). Please post the output from this command (you may want to black out any sensitive information such as passwords, IP addresses, etc. since this forum is regularly crawled by search engines).
If the ping test was successful but the curl test failed, something is preventing the proxy from connecting to vCenter on the specified host on port 443. Possible causes:
Typo in hostname
vCenter service not running on the specified host
Firewall between proxy and vCenter blocking port 443
vCenter service web services port changed at install time
This isn't an exhaustive list but these are the most likely.
I can ping our vCenter from the proxy, but the backups failed with the same error. We are on v7.4 and recently upgraded our proxies. Can you please assist.
bonnu06
2 Intern
•
258 Posts
4872
0
Posted August 13th, 2012 13:00
When you say typo in host name is it the typo of avamar proxy server name in DNS that you are talking about .