Doing a backup of the database, and restore it on the SQL server that the 2nd server will help.
The 2nd NPM that does not have the modules will just let it pass. If you just have Orion NPM, it should generally look at NPM tables in the Orion database, and should not factor in the rest of the tables.
But this will cause orphaned tables. You might need to clean up the database thereafter.
It should not be hard, as most of the tables will have some indication on the modules it belongs to e.g. prefixes VoIP will belong to IPSLA, etc.
Do you know of a Powershell script that will copy node and node event history from one SolarWinds database to another?
For various business reasons we need to copy nodes and history from one database to another database.
Both database are in use so we need to copy node and node event history from one SolarWinds database to the other.
We can't just overwrite the existing database.
This is very close bus does not do node history.