Hi Freddie,

I start by saying I haven't tested this myself, and the devil is in the details.

Even though technically you could setup another agent server connecting to the same SAP HANA env as documented here:

https://docs.microfocus.com/doc/MP_for_SAP_HANA/2.00/ConfigureOBMMPforSAPHANA

I'm afraid you may end up with duplicate CIs in OBM/RTSM of your SAP HANA, as you deploy the Discovery policy to the new agent, it will discover the same SAP HANA env and will send it to OBM. I don't think the CIs will merge. You may have to do some cleanup after.

You may want to try this on a dev env first.

Regards,

Faouzi Dahak  So would you say that this is not best practice because of the dup CIs in RTSM, and it would be best to remove old agent server config and deploy new SAP HANA setup and discover the saem DB instances? Also, is there away to use the current config and use to deploy to new server. My whole idea is to get off a 2016 agent server and use new 2019 server. thanks.

How long it will take to get the new 2019 Windows server? How long you can stay without monitoring SAP HANA?

One option would be replace the agent server with the new server with same hostname/IP as the current agent server, install the agent, change the coreid to the same coreid the current agent server has, request the cert from OBM and grant. 

At this point OBM will consider the new agent as the current agent, only few server version attribute changes in RTSM.

OBM has the assignment to this agent, you could redeploy with force to the agent server:

opr-agt -deploy -force -node_list <agent_FQDN>

When I do this in my env, the new agent server behaves exactly the same as the old agent server, and the monitoring continues where it left.

If you have a dev env, you may want to test it and let us know.