The AVamar proxy VM must be able to resolve and reach these locations using the Fully Qualified Domain Name: 1. the vCenter host 2. the ESX host for the VM being backed up or restored 3. the Avamar datastore
A crude test for connectivity would be to log on to the Avamar proxy VM. (root pw=avam@r) and verify successful pings the three locations above. This test would not reveal firewall issues however. Please test.
Also, these types of errors can be linked to the configuration of the Vcenter using an IP address instead of the FQDN, could you please check how the ESX server was registered to the Vcenter. Best pratice is to use the FQDN, if you used the IP address, there will be certificat errors because of hostname mistmatch. Please re-register the ESX host to the Vcenter using the FQDN.
Thanks for your help! It worked. I updated the resolv.conf and did the ping and nslookup tests. After that set up the Image backup once again and now it works!
rpervan
266 Posts
0
June 30th, 2010 03:00
Hi to all,
The AVamar proxy VM must be able to resolve and reach these locations using the Fully Qualified Domain Name:
1. the vCenter host
2. the ESX host for the VM being backed up or restored
3. the Avamar datastore
A crude test for connectivity would be to log on to the Avamar proxy VM. (root pw=avam@r) and verify successful pings the three locations above. This test would not reveal firewall issues however. Please test.
Also, these types of errors can be linked to the configuration of the Vcenter using an IP address instead of the FQDN, could you please check how the ESX server was registered to the Vcenter.
Best pratice is to use the FQDN, if you used the IP address, there will be certificat errors because of hostname mistmatch. Please re-register the ESX host to the Vcenter using the FQDN.
Thanks, regards,
.R
jboitel
1 Rookie
•
18 Posts
0
June 30th, 2010 02:00
Hi,
I have same problem but only with this build 258672 of vCenter 4.
look my post :
https://community.emc.com/thread/106462?tstart=0
jboitel
1 Rookie
•
18 Posts
0
June 30th, 2010 05:00
My proxy can resolve all FQDN.
The problem is elsewhere
If I uninstall the vCenter build 25...... and i reinstall. vCenter build 20.... the backup works !
alfredo_SnT
1 Rookie
•
51 Posts
0
July 8th, 2010 03:00
Hi Rej,
Thanks for your help! It worked. I updated the resolv.conf and did the ping and nslookup tests. After that set up the Image backup once again and now it works!
Alfredo
Hormigo
2 Intern
•
131 Posts
0
July 8th, 2010 16:00
Hi all,
For VMWare vSphere 4 Update 2 (build 258672)
Use:
Avamar Server 5.0.2.41
Avamar VM Proxy 5.0.105-169.
Regards,
Hormigo