Just getting back to this again....finally. RJHarris - you are correct! The reverse DNS information was not correct, or should I say not even there,I wish I was the admin of the DNS stuff again - but I am not going to get into that right now . After getting the DNS straightened out I can reboot the image proxy, reboot the Avamar server or restart Avamar services on the node and the proxies continue to work. Even went through a 7.1.0 upgrade on both the Prod and DR Avamar systems and they still worked. Now just working on getting the proxies upgraded now.
I wish I would have been told this during the Avamar deployment last year.
J-H end user - I tried refreshing the vcenter connection but it would not work with clients waiting. I did not want to cancel all the jobs and then start all the jobs back up again. On my reports the next day it throws me for a loop.
The key item here is your proxies are showing up as localhost. This means they lost their hostname information. This means you either manually edited them when you deployed them in the first place or they lost their DNS information.
The proxies heavily rely on DNS you must be able to run forward and reverse look up on their name. When they boot up they check DNS to get their name. So you can manually change but not recommended. Once you get the proxies back with their hostnames instead of localhost you should not have a problem and they should connect to Avamar just fine.
Anonymous User
1 Rookie
•
55 Posts
0
November 12th, 2014 09:00
Just getting back to this again....finally. RJHarris - you are correct! The reverse DNS information was not correct, or should I say not even there,I wish I was the admin of the DNS stuff again - but I am not going to get into that right now
. After getting the DNS straightened out I can reboot the image proxy, reboot the Avamar server or restart Avamar services on the node and the proxies continue to work. Even went through a 7.1.0 upgrade on both the Prod and DR Avamar systems and they still worked. Now just working on getting the proxies upgraded now.
I wish I would have been told this during the Avamar deployment last year.
J-H end user - I tried refreshing the vcenter connection but it would not work with clients waiting. I did not want to cancel all the jobs and then start all the jobs back up again. On my reports the next day it throws me for a loop.
Thanks again!
J_H_
2 Intern
•
498 Posts
1
October 10th, 2014 13:00
you need to refresh your vcenter connection
go to the administration page
Services Administration tab
drill to Utility Node
find the line for your vcenter
right click
choose restart (even if it says it is ok) to have Avamar re-connect (read) your proxies from vcenter.
RJHarris1
21 Posts
0
October 10th, 2014 13:00
Brent,
The key item here is your proxies are showing up as localhost. This means they lost their hostname information. This means you either manually edited them when you deployed them in the first place or they lost their DNS information.
The proxies heavily rely on DNS you must be able to run forward and reverse look up on their name. When they boot up they check DNS to get their name. So you can manually change but not recommended. Once you get the proxies back with their hostnames instead of localhost you should not have a problem and they should connect to Avamar just fine.
Richie