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

Move Nodes and historical data to new NPM/DB

Hi,

we are going to install a second NPM along with EOC. We intend to move about 500 nodes including historical data to the new NPM/DB. Is there a procedure for that or has anyone done this before?

Thx

Klaus

Find more posts tagged with

npm_move_nodes

Accepted answers

All comments

bshopp

Have you looked at this?

mark_wiggans

To reassign nodes to a different polling engine:
1. Click Start > All Programs > SolarWinds Orion > Advanced Features > Orion Service Manager.
Note: Confirm that you stop the SolarWinds Network Performance Monitor Service on all polling engines.
2. Click Start > All Programs > SolarWinds Orion > Advanced Features > Monitor Polling Engines.
3. Click Servers > Poller Load Balancing, and then select the nodes you want to reassign.
Note: Use Shift + click to highlight multiple consecutive rows, and use Ctrl + click to highlight multiple non-consecutive rows.
4. Click Polling Engines > Move Selected Nodes to *, substituting the target polling engine for *. The node is reassigned, and it reflects the name of the polling engine in the polling engine column.
5. Click Start > All Programs > SolarWinds Orion > Advanced Features > Orion Service Manager to restart Orion NPM services.

expereo

this is about moving the database to another server.

I want to move selected nodes including historical data...500 out of 2500.

expereo

I thought that might only work to move nodes to an additional polling engine feeding into the same database.

Please confirm that this procedure works between 2 standalone NPMs with separate databases only connected by EOC.

njoylif

I've done this several times - for various reasons. The easiest and safest thing I've come up with is to shut NPM down, copy the DB to a different name (or same name if different machine), then bring it up on the new server. I've found I must do it with nothing connected to the NetPerfMon DB while attempting.

This allows you to keep the original DB in tact for fail-back as well, and if your doing an upgrade, you can install the older version of NPM on the app box and point it to the new DB, then upgrade.

FormerMember

So will this will keep all the settlings, the interfaces that are beinb monitored or not monitored? i have about 8000 nodes to move. seeing if this will work./