jarevalo

Our primary concerns with a central location was that it will have a lot of overhead on the WAN by polling every couple of minutes. Also a single point of failure. Currently we have configured it to have alerts if neighboring ORION goes down.

Can we have multiple Orion instances using a single database to have the same UI? Following is an instance from the ORION installation guide: Scalability By adding individual polling engines, you can scale your SolarWinds NPM installation to any environment size. By sharing the same database, you can also share a unified…

Thanks for reply. Sorry i am a bit confused here. Which approach is being referred to here? Have you tried the manual way of exporting it across and then managing it?

Thanks Harvey for the suggestions. We will look into it and see if it is a possibility or requirement at the moment. We are trying to have a standard template to start off with and then go from there. Not looking into an investment into another product, right now. The manual way be hard to manage, but will be a good start…

Thank you very much for the information. We are getting new hardware and separating out the SQL.

Please discard my last question. Found it. Does that back up the whole web interface without any configuration of nodes or interfaces?

Is there any known issues that it might cause having one template across all the server? Does it require any initial changes before having it fully functional apart from the cleanup of thing?

Where can i access the utility? I couldn't find it on my Orion server or the web console. Can you please specify the location of the utiliy? Much appreciated

Thanks mharvey for the reply. We wanted to have a standardized web interface across our Orion servesr. Where can we access the inetpub\Solarwinds directory? Do we need to export it and then import to each of our server?