topic Re: An new ActiveGate Deployed after a second node has joined the cluster. Would OneAgent installed prior to adding second node smart enough to know the existence of new ActiveGate? in Open Q&A

An new ActiveGate Deployed after a second node has joined the cluster. Would OneAgent installed prior to adding second node smart enough to know the existence of new ActiveGate?

waikeat_chan — Mon, 13 Dec 2021 10:28:53 GMT

Client want to move the Dynatrace Managed to new set of servers.

They:

a) don't want reinstallation of OneAgent

b) don't care about historical data

Thus, I proposed them to add the new set of servers to join the cluster of existing Managed, then deployed a new ActiveGate, then remove the old existing Managed follow by removal of old ActiveGate.

Would it works?

Best Regards,

Wai Keat

Re: An new ActiveGate Deployed after a second node has joined the cluster. Would OneAgent installed prior to adding second node smart enough to know the existence of new ActiveGate?

skrystosik — Tue, 19 Feb 2019 16:22:01 GMT

I think this will not work without reinstallation of Agents. You will not have to do it when server IP adresses will be the same.

Sebastian

Re: An new ActiveGate Deployed after a second node has joined the cluster. Would OneAgent installed prior to adding second node smart enough to know the existence of new ActiveGate?

david_n — Tue, 19 Feb 2019 16:29:02 GMT

Hello Wai,

If it were a new AG on the existing managed instance then you would be fine and the agent would see the new AG and add it to the connection list. The issue is that you are adding a new managed instance which means you will have to install agents from that instance as a best practice. Agents are built to connect to the instance that they are downloaded from.

Thanks,

David Nicholls