Hi all, I am a new user to Solarwinds - I have a 2008 VM server with Solarwinds NPM12 installed, tied into GNS3 with 8 routers 4 switches and a few servers. All working fine.
Solarwinds is indeed a powerful tool very impressed so far - planning on using this lab setup to go through the SCP asap.
However I have been given 3X Dell PowerEdge servers to be used for Solarwinds & Tasked with moving an existing VM solarwinds to the 3 previously mentioned PowerEdge servers.
These servers I'm lead to believe have bear bones server 2012 in preparation for SW.
Any suggestion on where to start? What would each server be used for? Application/DB and backup?
Is there a guide somewhere for utilising all 3 servers for this and what needs to be installed on what?
Sorry if this is a bit vague, talk about baptism by fire!
Solved! Go to Solution.
Hi all, thanks so much for your help.
I have successfully migrated away from 1 VM box to 3 Physical servers.
1 for NPM
1 for NTA
1 for DB
All 3 servers 32gb ram 3.8ghz 16 logical cores. So much better than 1 3ghz server with 8GB ram!
Only 1 sticking point was, the host name for the NPM had to much exactly or the NTA would not function, it does state that in one of the guides above. For a new install it would be fine, but i migrated the db so it was looking to match the host name.
Also been sent on a Solarwinds course for a week & after that (5 weeks after, for more study/lab time) passed my SCP exam
Hi there gazwales! If you need to complete migrations of data, moving of products, and need a few checklists, we have new Migration Guides!
These may give you some important walk-throughs and helpful tips.
It depends on what modules you have. The basics would be one server for NPM and most if not all modules, one server for SQL. The third server depends a bit on what modules you have. For instance, if you have NTA, you would want one server for the Flow Storage Database, while NTA itself gets installed on the main server. Or if you have a ton of sites and need an additional poller this third system could be used for that.
Now, one thing that might be smart is to make at least the NPM server at its base a VM server, if not all of them. That way if you decide to get any of the "non-integrated" modules, like LEM or Firewall Security Manager, you can install them as VM's on the same physical hardware as the main solarwinds poller, but give them their own OS. LEM comes as a VM package with its own OS, FSM requires windows...
From what I understand, making them at their base a VM system would also allow you to use vMotion to move them from server to server if needed...
To begin with for sure unless you're a small network put your real SQL Server not express on it's own VM or box. Also if you're using NTA note that it now has it's own noSQL database as well (do not put the two databases on the same box or VM). NPM, SAM and whatever modules you are going to run will be on your main poller and any additional pollers if you have them. Pollers can be on individual box/vm's but can also be stacked on the same machine in which case they'll use the same IP address as a source.
Hi gazwales and welcome to THWACK!
I would recommend that you go over the NPM Get Started Guide:Network Peformance Monitor Getting Started Guide - SolarWinds Worldwide, LLC. Help and Support in the success center paying close attention to the "Plan your product deployment" article.
As for THWACK, I would highly recommend checking out the Getting Started section and completing the "You Don't Know THWACK" mission to familiarize yourself with THWACK and get a good chunk of points to start out with.
This looks like the answer that I was gonna hunt for as well! Thank you so much for posting it.
Just wanted to give a shout out to the forum as well as a new Solarwinds and Thwack user. Been kind of lurking and not posting for a while, but time to come out of the woodwork and learn!
So, hello all!
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.