Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Netflow Traffic Analyzer (NTA) > Hardware replacement on NTA Flow Storage Database

Hardware replacement on NTA Flow Storage Database

Table of contents
Created by Daniel Polaske, last modified by MindTouch on Jun 23, 2016

Views: 5 Votes: 0 Revisions: 5

Overview

This article provides brief information on replacing hardware components on the dedicated servers hosting the NTA Flow Storage Database occasionally as part of the normal break/fix life cycle of any server. 

 

Simple non-disk component replacements which simply require powering down and powering up the server are covered in the steps below.

Environment

NTA version 4.x

Detail

You can stop the Netflow Collector services on your NTA Collector server to preserve processing and memory usage as no flow data will be able to be stored if the NTA Flow Storage Database is offline.

No other action is needed from the SolarWinds software side. 

 

The NTA Collector and NTA Flow Storage Database services will simply re-connect when the NTA Flow Storage Database is brought back online, provided no configuration changes have been made using the Solarwinds Configuration Wizard or NTA Flow Storage Configurator.

 

 

 

Last modified
20:33, 22 Jun 2016

Tags

Classifications

Public