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 do you deal with equipment change out in NPM?

When we upgrade equipment or a customer discontinues service the old equipment appears as down in NPM. Is there anyway to retain data or export data of a node prior to deleting it? The equipment might come back into inventory and be installed at another location. The old data for customer X is not valid or relevant to customer Y. It would be nice if we get a request 6 months down the road for Customer X usage stats to have that data someplace.

-Ken

Find more posts tagged with

Accepted answers

All comments

adatole

It's certainly possible to export your solarWinds data (in general) to another database. All it takes is time and storage.

If you are thinking of doing this, you will want to do it regularly and understand this about the Solarwinds data structure:

<blahblah>_detail is the every-5-minute collection (or whatever you have collection set to be

<blahblah>_hourly is the rollup data contains the _detail data and summarized it to hourly averages after a week

<blahblah>_daily is the rollup that takes the _hourly data and summarizes it to a daily average after a month.

<blahblah> is usually NOT a table, but a view that combines those other 3 tables into a single coherent set of data.

SO... if you are going to start exporting data, you want to focus on the _detail tables only (with exceptions, but you hopefully get my point) and just grab all new records since the last export.