Just looking for user experience on anyone that has upgraded to NCM 7.3 since it went GA. We've had some past bad experiences with major point upgrades so I want to see what others have experienced so far on this upgarde
I have been running it since RC without serious issues. As far as user experience.... MUCH better speed wise.
we are searching for some experience with upgrade from NCM 7.2.2 .... did anyone the upgrade? - What will happen with the single databases after merging to a single one?
Hi otto,
The NCM data will be migrated to the NPM/Core database. We recommend to back up your data before the upgrade, but after you complete the procedure successfully, the NCM database is no longer needed.
Regards,
Jiri
I participated in the RC program. There were no issues and some really good things about the new version. I really like how much better it is integrated with NPM 10.7. I did have to upgrade NPM from 10.6 to 10.7 before I could install NCM 7.3.
Database merge was seamless. My only issue was partway through the NCM upgrade it wanted to reboot. I didn't expect that. I asked support before I proceeded. I ended up allowing the reboot and the install just picked up where it left off. I wasn't sure it would since I was RDP'ed into the server.
How many network node elements are your teams migrating? We have a bit over 5000. We seem to run into a lot of issues during migrations because of the size of our deployment.
i upgraded from 7.2.2 to 7.3 and here are my lessons learned (about 150 devices)
the upgrade was expected to be .50 - 1 hour + according to the installer, it actually took about 5-10 minutes
i ran into a weird scenario poller wise. 7.2.2 hit the devices from the poller NCM was installed on, not the case with 7.3. with the upgrade if you are running an additional NPM poller (which i was) you will need to install an NCM additional poller also. since i had not done this and i restrict TTY access i had to migrate everything from the 2nd poller in NPM to the first so that i could run the script to update the TTY ACL to allow the 2nd poller access. then i had to migrate these same devices back to the additional poller. once i did this it worked like a champ!
We currently have our NPM DB and NCM DB on a common Database server seperate to our Solarwinds Server. Has anyone had any issues with the merging of the two databases?
Obviously backups will need to be done etc before we go ahead with the upgrade, just eager to hear other peoples issues and concerns if they have any
yes i upgraded it and it works!
Otto,
Have you upgraded to NCM 7.3 yet ? We have 4 additional pollers, and just upgraded from 7.2.2 to 7.3 and are trying to determine if its possible to rollback due to the workload created. Each of our pollers manage approx. 1,000 nodes, but historically we've always had NCM running only on main engine in a centralized fashion. Node status / statistics was distributed, but backups were centralized. This was due to ACL's and other issues not yet remedied with the merge of multiple health organization (which we are). 7.3 distributes NCM functions, like backups to the same pollers that is managing the node. No exception possible. Be sure that your additional pollers and the nodes they manage, have no issues using the protocols you use to backup (telnet, ssh etc). Performance however on 7.3 is great, I just need to make a decision after assessing issues from 7.3 if we work through the issues, or seek advise from solarwinds on how to roll back.
Epenney
I upgraded and found that out too. I'd say there is not going back with out dumping your existing data because it moved every thing into a single database with NPM as well as changed a few table names. The only way I can think of a roll back would be to use a backup copy of you SQL databases from before the upgrade and then uninstall NCM 7.3. In reality it's probably less work to move forward and fix the ACL's
