Jiri,
Through a current NCM case (# 780242), I'm now getting conflicting information (shown below in italics) from what you provided about upgrading/integrating 7.2.2 (from a standalone system) to 7.3.2 on our primary NPM 11.0.1 system with different server and ip address. I'm being told to install 7.2.2 on the NPM 11.0.1 primary poller first, then upgrade NCM to 7.3.2 if we want to preserve the historical 7.2.2 data and NCM settings. I may have misunderstood your reply, that I could install 7.3.2 (new install) on the NPM 11.0.1 server and it would prompt for the old 7.2.2 database and merge all the historical data and NCM settings? Did I misunderstand? Can you please clarify what is the proper approach? You da'man so I wanted to get it straight from you.
"If you're planning to migrate NCM from a 7.2.2 stand alone into a 7.3.2 integrated deployment, it isn't as simple as doing both the upgrade and migration at the same time. Instead I would recommend that you first migrate the 7.2.2 NCM installation and integrate it with the Orion database over on the existing NPM server first. This process will require you to perform a node sync after you have completed the NCM 7.2.2 installation. This way once this 7.2.2 install is up and working, then you can complete the 7.3.2 upgrade, and still have all the NCM data available.
If you try to migrate and upgrade in one step, it won't work for this NCM upgrade, because there is no way for the NCM 7.3.x installation to connect to that old NCM database. And since you want to integrate it, we need to do that step back in 7.2.2 before the 7.3 upgrade."