This post is more than 5 years old
1 Rookie
•
61 Posts
0
4357
May 1st, 2017 12:00
How to set up 2nd Avamar system with DPA
We currently have 2 Avamar and Data Domain systems.
Our main Avamar and Data Domain is already set up with DPA and generating reports.
Our 2nd Data Domain system I was able to easily add in DPA however our 2nd Avamar system I am not able to. When I run Discovery, it does not find our 2nd Avamar. How do I add our 2nd Avamar in to DPA so I can monitor those VMs, backups etc as well?
Thank you!
No Events found!
kmbay
1 Rookie
•
61 Posts
0
May 2nd, 2017 10:00
Thank you. Previously I did not go through and finish, I just stopped at the Start Test phase.
This time I went to Discovery Wizard - choose Backing Application, EMC Avamar and entering the hostname of our DR location Avamar (our 2nd avamar system). I start the test and it returns with following error:
Performing tests for EMC Avamar:
Test failed! Unable to connect to host with the given host name and aliases. Please, verify that the DPA server has access to the host with the name and aliases.
Even though it failed with that, I still proceeded through all the other steps till Finish when is said "Discovery is complete. The system automatically added the discovered objects to the Object Library and selected destination groups."
After running the Debug as you suggested I get the following error:
Time : 5/2/2017 2:04 PM Eastern Standard Time Log Level : INFO Message : Request run created by component "ModTest Request"
Time : 5/2/2017 2:04 PM Eastern Standard Time Log Level : ERROR Message : No collector is installed or collector configuration is unavailable
kmbay
1 Rookie
•
61 Posts
0
May 2nd, 2017 11:00
How do I check the Data Collection Agent? DPA was set up for us by EMC so I cannot even recall how our 1st production Avamar was set up to integrate with DPA. Although oddly enough our DR (2nd) Data Domain was found and discovered. It is just our DR Avamar that is not.
kmbay
1 Rookie
•
61 Posts
0
May 2nd, 2017 11:00
I only get Local Agent option - Remote is grayed out. On Next I get that 2nd pop up error.
I went to our DPA collector server and ran telnet to our 2nd avamar on port 5555. It opened a telnet window to that Avamar server.
I went back to DPA and ran a Job Monitor debug and I received the same failure errors:
No collector is installed or collector configuration is unavailable.
This is b/c I noted in Inventory that this Avamar is using itself (own hostname) as Collector Agent rather than my specific DPA server (as my 1st Avamar system correctly is).
How do I get my DPA to allow me to use the Remote Agent option so I can select the correct DPA Server Collection agent vs a non-existent agent on the Avamar system? Or rather now that I've already discovered this 2nd Avamar and it is listed in Inventory, how do I configure it to use my Data Collector Agent rather than it's own server name?
kmbay
1 Rookie
•
61 Posts
0
May 2nd, 2017 12:00
That did it. Thank you Lauren!!
Can I correctly assume that the DPA will only start collecting backup data from this point on for my 2nd Avamar and no data prior to today?