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

How to split Solarwinds components to different servers?

Current configuration on server1: NPM 10.1.1, APM 3.5, NCM 6.1, NTA 3.7, IVM 1.0.0.

server2: SQL 2005 Std

We would like to move APM to its own server to lessen the polling load on server1. We have 2 new servers (physical) to put the apps on. We are also licensed for the Enterprise Operations Console.

Our goal is to have NPM NCM, NTA on one box and APM and possibly the Ops console on another. The database will remain in server2. We will be upgrading to the latest licensed version at the same time.

What is the best way to do this without losing configuration and historic data. And minimizing down time? Do we install APM on the new server and uninstall from the old? Am aware about exporting and importing certs.

I am thinking it might be better to migrate everything to one new server, and then split off APM.

Any help would be appreciated. I have about 20 days left in the lab environment to get this tested and documented, and ready for production install.

Find more posts tagged with

Accepted answers

All comments

mavturner

dflager,

Are you completely set on splitting out APM (now SAM) from NPM? If you have the new hardware I think you will be much better off moving the most resources you can to the database server. The recent versions of NPM and SAM both have good performance improvements. Also, instead of using EOC and splitting your deployment, it would be better to have an additional polling engine to balance the polling load across multiple servers (assuming that is a current bottleneck and it's not all in the database).

Have you opened any tickets about your performance issues?

Mav

dflagler

Haven’t opened any tickets. Main issue is the time to complete a poll of all devices. We get gaps sometimes in the charts. The Network Trends page doesn’t finish loading before the screen refreshes. So splitting off APM/SAM would remove some of the polling load from the NPM server. This is one of the configurations suggested to us last year by Solarwinds, which is why we purchased the ops console. I can move APM to spread the load and use the ops console which is way cheaper than paying for another polling engine license. The SAM load is only going to grow. Currently have about 2039 component monitors, but have only 47 of more than 250 servers configured for APM. NPM on the other hand polls 591 nodes, 1066 volumes, and 2478 interfaces.

We are moving from an 4.5 year old server to 2 brand new ones, so performance out of the box should be better.

Dave Flagler

djassi

It would be useful if Solarwinds had deployment scenarios involving the many products it has. Sort of a best practice for product deployment.

There should be recommendation around what should go together on servers and what is not recommended. It would be easier to actually gauge what is needed in a particular deployment. I might be wrong, but I don't think this document or something like it exists.