Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Question about moving NPM and NCM to new server

I am planning to upgrade my NPM/NCM server to new hardware. I have some questions about how to do so without loosing much polling data.

Here's what I have on the Orion server.

NCM 5.5.1w/500 devices

NPM 9.5 SP4 w/~1800 elements

Engineers toolset

CatTools

SQL server is on a separate server. Database will remain on existing SQL server.

New server will be 64 bit windows server 2008.

I have read through the migration guide for NPM, but I still have a few questions.

I want to be able to move 1 or 2 nodes to the new server, let it run for a half day or so to make sure everything is working correctly on the new server.

Once everything looks good on the new server, I then want to be able to move the rest of the nodes over to the new server.

Here's my plan. I'm hoping for some feedback on this plan to see if it is a good plan or not.

1: Install NPM eval copy on the new server, attaching it to the existing database.

2: Move 2 nodes over to the new server(poller) using the Monitor Polling Engines application, and let it run for half a day or so to make sure there are no problems or issues. Resolve any problems with SW support before moving forward.

3: Install Full version of NPM over top of the eval version, and manually register it on SW website. (have to do this manually due to proxy server)

4: Use the Monitor Polling Engines app to move all the remaining nodes to the new server(poller)

5: Uninstall Orion software on the old server.

I'm hoping to do this as smoothly as possible, without any hiccups. So I'm hoping that others may have done there migration in a similar fashion and can suggest things to look out for or better ways of doing it.

Thanks,

Jeremy

Find more posts tagged with

Accepted answers

All comments

bshopp

I am looking into with the Dev team insight how best to do this, but the first fatal flaw I see is two Orion's cannot share the same DB

bshopp

One suggestion would be to duplicate your database, point the eval at that. Let both run. Upgrade the eval to production when comfort level is reached.

jcooler

One suggestion would be to duplicate your database, point the eval at that. Let both run. Upgrade the eval to production when comfort level is reached.

Thanks Brandon. 3 more questions for you on that.

1:) I thought the eval copy could use the same DB, and act like a additional poller, until I register it. It sounds like that is not the case. (Please confirm).

2:) Also, If I do the method that you suggested, would the duplicate copy of the DB become the production DB once I activate the eval copy and deactivate the old copy?

3:) How do I duplicate the database? I do not have full access to the SQL server, as our DB admins handle that part. However, I do have access to the database via SW Database Manager and via SQL Server Management Studio Express. Is this something I will have to have one of the DB admins do?

Thanks again,

Jeremy

bshopp

#1 - no that won't work, you will hit a slew of issues

#2 - It could if you wanted it to be, depends on when you cut stuff over, how much you cut over etc. Might make sense to PM me and talk offline on this

#3 - I would engage your DBA