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 SolarWinds to new Data Center......suggestions?

Here is the scenario.

My company was bought out by another, and they have ~4 times more nodes. They do not have a compressive monitoring system but, they love what SolarWinds does and how I have been maintaining it for the last five years.

THE PLAN:

To rename|reIP|new domains the old side (my old side).
Move the license and nodes to their data center and start from scratch. Even moving the dB over would not help as everything will be new and I don’t want to spend the next 10 years scrubbing dead crap from the dB.

Here is a list of our SW products: NPM, SAM. WMP, NCM, NTM, SRM, VNQM, VMAN, NTA

THE QUESTION:

What would you document or move to successfully bring up the new SW environment?????

I was thinking a list of SAM templates in use and a list of active alerts. I would not export the alerts as it is an xml file with all the wrong info and nothing will be the same of the other side.

Copying the WMP scripts so I know the steps to recreate. I have ~160 of these.

Let the network team take care of NCM, NTM, NVQM and NTA

Let the storage team take care of SRM.

I will need to set up a new service account for SW to access Windows nodes and set up a new snmpv3 account for all the Linux and network stuff.

What am I missing and how would you do this????

Find more posts tagged with

Accepted answers

All comments

adam.beedell

Big question!

May come back to this later. Short stuff I'd consider would be a bit less technical and a bit more organizational

Understand their name format and IP structure asap, figure how that impacts dynamic queries or whatever you've got in your env at the moment
Find their data sources
Get connected nicely to their stakeholders, get them onboard and on your side

Creds

JP_net

We do this kind of work for clients all the time. For starting from scratch, I would definitely have an understanding of Custom Properties (why, where, who. not necessarily the actual values to nodes), back up you alerts (they can be a good starting point since you are familiar with SW and capabilities), back up reports, Save off any custom widget configuration (all mine are written in SWQL. It is easy to back up in .txt) to name a few. I think you are on the right track, but this is going to be a bit of a process.