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
Store

Question on migrating NPM to another server

I've got an installation of Orion NPM, APM, and NTA on a test server running a SQL server on the same machine. We're thinking of moving the NPM and modules to a different server, and adding memory to the current machine. Should I get all the modules installed before pointing the new server at the database, or should I go ahead and install the NPM, point that at the new database, and then install the other two modules?

Thanks

Find more posts tagged with

Accepted answers

All comments

justsomeguy1988

It may be worth considering moving your SQL server to a different server vs. moving Orion and modules. That way you can spec and tune your SQL server to address performance bottlenecks that are more common to database servers, i.e. I/O, memory, and CPU. Also, then you will only have to rerun your Orion Configuration Wizard and point it to the new SQL instance.

Just a thought.

Steve_Pfister

But, wouldn't I be able to do that if I move NPM and the modules? SQL would be the only thing left on the current server.

Thanks!

mark_wiggans

Yes, but with many more steps involved inlcuding having license resets made available.

• Installing Orion NPM on the new server
• Reassigning nodes to the new polling engine
• Moving custom maps to the new server
• Moving custom reports to the new server
• Updating report schemas
• Uninstalling Orion from the old server

and then running the Config. Wiz. and pointing back to the DB-

www.solarwinds.com/.../OrionServerMigration.pdf