Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
This article provides information on rebuilding and migrating your Orion Poller configurations.
You may refer to the SolarWinds Migration Guide document for additional information regarding SQL and NPM Migration.
The guide includes the following documents with prep lists and checklists, including steps for the poller migration:
Review Best Practices for Managing the Orion Platform Database for information on SQL best practices and performance tuning.
The whole Orion Database, including all data polled and settings reside in the database.
But there are a few folders that may have customizations and should be backed up.
All NPM versions
If you are migrating Orion Poller to a new IP address:
For additional information, refer to Configuring Devices for Flow Collection.
Refer to the Deactivating and Activating Orion Product Licenses during Migration article for the procedure.
The ability to move monitored nodes between polling engines is now a feature of Web Node Management (NPM v10.2 onwards).
Do the following steps to change the polling engines:
If you are migrating a new poller, but keeping the name or IP, after the migration it is likely that it is still recognized as if it is the same server.
This can be seen in Orion Website > Settings > Polling Engines.
Or, open Orion DB Manager or SQL Management Studio and run the following:
SELECT TOP 1000* FROM [dbo].[Engines]
If the engineID is the same, no action is needed. For some reasons, the migration picked it up as a NEW Poller.
Then a new engineID record will be created and you will have to follow the node migration process to migrate the nodes from the old to the new poller's engineID.
Refer to the screenshot below on how delete old polling engines via web console:
Refer to the SolarWinds Migration Guide on how to delete old polling engines via database manager.
Web-based Report Scheduler
You can upgrade to NCM 7.2 first before the migration. NCM 7.3.x merges NCM and NPM database into 1 DB and simplifies the migration process.
FSDN Configurator on FSDB database server and NTA Application server.
Here you can choose: