NPM 9.1 -> 9.5 with new DB and new pollers

I currently have Orion 9.1 SP4, with two additional web servers, three additional pollers, and a hot standby poller, all running on server 2003, back-ended with a SQL 2000 database. I also have Orion NCM running, back-ended on the same DB server

I'd like to bring all this up to the latest versions of all the installed software. In doing this, I need to move the database to a SQL 2008 DB server (run by our extremely efficient DBA team, instead of an overworked network admin ), and also move all the pollers, additional web servers, etc to Server 2008 to be in line with our new corporate standards. When I move to Server 2008 for the pollers, etc the server names will change since the servers will be running in our VMWare ESX environment.

I need to know the best way to do this. Do I just take everything down, move the DB, and then reinstall the pollers, etc on the new servers, and then remove the references to the old pollers? Do I upgrade the pollers in place and migrate them to the new server?

Help!

Find more posts tagged with

sql_2008

server_2008

orion_9.5

upgrade

Accepted answers

All comments

bshopp

Have you seen this doc here

GregD

Thanks for that :-) It answers half my question, I suppose. I guess I would do this procedure to move the DB, then install the new 9.5 pollers on the new VMs, and then run Poller Load Balancing to move the nodes to the new pollers. I guess the only question that remains is how to get the references to the old pollers out of the database once I'm done with them - the same with the Hot Standby and additional web servers.

On a side note, can NPM 9.1 SP4 (or SP5) work with a SQL 2008 backend? That might be a good intermediate step if it can.

bshopp

No, only NPM 9.5 support SQL 2008

Congo

I am not sure about the hot standby and web servers, but I know that once you have moved all nodes from a poller, it will ask if you want to delete it from the database.

rsprim

Greg,

I can't remember where (probably here on Thwack) but I read that you need to upgrade your 9.1 SP4 pollers to 9.5 prior to swinging your new 9.5 VMs over to your new SQL 2008 server. We are doing something similar and are setting up synchronization from the old database server to the new one, planning to upgrade our 9.1 Pollers to 9.5 (probably after SP2) and since we have two we will hopefully keep one working while we rebuild the other to 64-bit standard. We will be renaming as well and unfortunately all of our servers are not connected to the internet so we will need to put a call into customer service to reset our licenses to free them up for the new server build and naming convention that we are using. Hope this helps.

Rob

GregD

The only issue with that is that I'm running SQL 2000 and going straignt to 2008 because of time and bugetary concerns. If I was able to make a stop at SQL 2005 along the way I would upgrade to 2005, upgrade to 9.5, then move to 2008.

Right now my plan of attack is to shut down the entire Orion system first thing in the AM, then migrate the DB, install 9.5, and migrate the nodes to the new pollers. It'll be an entire day of work but at least I know it will be done right