Applications Systems
Migration steps to migrate WPM to another server or polling engine
This article goes over crucial steps to migrate WPM to a new server or polling engine. Often SEUM Agents will no longer responding after migrating WPM to another polling engine if these steps are not followed.
First published date
Last published date
Overview
The problem is that the SEUM agents are still pointed to the old engine and need to be updated.
This update should normally occur in step 8 of the Orion Platform Migration Guide; the same step where SQL Queries are run to update the database with new server hostname information in the normal Orion Platform migration process when Migrating to a server with a new IP Address and Hostname.
Product section
Cause
The SEUM agents are still pointed to the old engine.
Resolution
Step 1
Verify the Engine ID's in the database and which Engine ID is assigned to the SEUM agents:
- Go to Volume:\Program Files (x86)\SolarWinds\Orion\DatabaseManager.exe.
- Right Click and open it as administrator.
- Click Add Default Server.
- Expand your Orion Database.
- Right Click and Click New Query.
- Copy and Paste the Below Query:
-
SELECT TOP 1000 * FROM [dbo].[Engines]
To see what EngineID was assigned before to those agents clear the query and copy and paste the below in:
SELECT TOP 1000 * FROM [dbo].[SEUM_Agents]
Step 2
Update the Polling Engine IDs:
- Copy and paste the below query in Database Manager, replacing NewEngineID with the New Engine ID, and OldEngineID with the Old Engine ID.
UPDATE [dbo].[SEUM_Agents] SET PollingEngineID = NewEngineID WHERE PollingEngineID = OldEngineID
Notes and Clarification:
- SET PollingEngineID = NewEngineID, the NEW polling engine ID.
- WHERE PollingEngineID = OldEngineID, the OLD polling engine ID.
UPDATE [dbo].[SEUM_Agents] SET PollingEngineID = 1 WHERE PollingEngineID = 2