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

Moving Primary Poller

I have been moving our additional pollers lately onto new hardware. This has been straight forward - I have just been installing another poller, and then using poller load balancing to move all the monitored devices onto the new poller (poller load balancing prompts you to remove the old poller from the engines table when there are no devices left).

I've now come to the primary poller which also has a number of modules installed (VoIP, APM and Netflow). I'm assuming that I can't install another instance as I have been with the additional pollers. If that is correct, what is the best process to move the primary poller and the modules?

I was thinking of shutting down the primary server, removing the row from the engines table manually, and then doing a new install on the new hardware (including all the modules). Then as a last step using the poller load balancing function to move the devices. Is this the most logical/best method? Does anything need to be done for APM and VoIP?

Dave.

Find more posts tagged with

Accepted answers

savell

Well, after a few hours looking at this, and then another couple working with support - I didn't get anywhere.

Then I came across this http://support.solarwinds.com/kbase/ProblemDetail.cfm?ID=1118

At least APM is now working.

Dave.

All comments

savell

Anyone done this or have any advice?

Dave.

FormerMember

I asked some of our experience Support folks, and here's what I got.

What he already mentioned is the best practice, but I would not recommend going into the engines table, and deleting the old engine id. I would recommend doing a new install of the main Orion, and all of the modules he has purchased. Once that is done, than run through the configuration wizard connect back to the original database and finish out the wizard. Once that is done then I would then use the poller load balancing to move all of his device from the old engine id over to the new one. This is a cleaner method, as the option of having him remove the engine id before doing the migration has not been tested, and could cause a lot of problems.

Nothing should need to be manually moved for APM, or VoIP. Everything for those two modules should be saved in the database so when he reconnects back to the original database it should still contain all of his settings, and data for those modules listed.

savell

Thanks for taking the time to follow this up Denny.

Will do as suggested and let you know how it went.

Dave.

savell

Mmmm..

The poller moved OK, however neither the APM or VoIP modules seem to want to poll anymore.

It seems like the Voipengines and APM_BusinessLayer tables weren't updated with the new install.

Have a call in with support #115524

Dave.