We're coming up on the need for multiple pollers, and the new pollers will be placed in WAN-separated sites. Naturally I'd like to keep the WAN chatter to a minimum, so I'm wondering how people before me have prevented this from being an issue, since -- as I understand it -- each remote poller will want to frequently discuss life with the main DB located on our first/main Orion server. Some questions:
Firstly, is this even a real problem? Do remote pollers chat that much with the DB? Assuming they do, what seems to be the best solution?
The fix I was thinking about was clustering the DB servers and letting each site chat locally, then letting the DBMS replication do the dirty work at some stately scheduled pace. Of course the problem there is that the data is no longer "live", but at least each local copy is, which also soothes my desire for CYA backups. Aside from the update delay you also have an alert-awareness delay, but adding remote pollers to the show pretty much guarantees a delay somewhere, so you may as well try to mitigate the delay duration and location. (As an aside, might there be a way to perform a similar trick with Patch Manager, so that remote hits on that DB are faster too?)
I've read the basic Solarwinds docs, but I wanted to hear about real-life experiences. What are the issues, options, etc. you've run into, and what does / doesn't work?
(If this has been beaten to death before, just point me that-a-ways.)
Thanks!
Curtis