Submit a ticketCall us
Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Recommended configuration setup and tips for NPM v11.5 with NetFlow

Recommended configuration setup and tips for NPM v11.5 with NetFlow


To avoid performance issues with the server, these are the recommended configuration setup for NPM v11.5 with NetFlow:

  • RAID 1 C: drive (Operating System) (2 drives)
  • RAID 10 or 1+0 4 drives (This is striping and mirroring combined)
  • RAID 0 E: drive (SQL logs) (2 drives)


The following documents can also be used as reference for SQL sizing and performance tuning:


  • NPM v11.5

Best Practices for RAID 10

SolarWinds' recommended solution is:

  • 2 X RAID 1 disk (Mirroring): For the Operating System
  • 2 X RAID 1 disk (Mirroring): Place the pagefile here and can also be used for applications and some ad hoc programs.
  • 4 X RAID 1+0: Striping and Mirroring for database files (2 partitions; 1 for the data file and 1 for the log file).
  • Set the database to be used as SIMPLE and not FULL recovery. 


Additional Information and Tips

SQL server performance is a hot topic especially if it is being leveraged for high performance Network Management Station (NMS). This can become even more critical if applications such as NetFlow are added, which tend to carry a significant input/output (I/O) burden.
Some organizations rely on their Database Administration (DBA) team to own, maintain and optimize the database servers.

For those without DBA teams, here are a few tips to optimize your SQL server:

  • Add more Random Access Memory (RAM). It does not really matter how much you have, but adding more would always help.
  • Just say NO to RAID 5. It is great for application servers but horrible for database servers where I/O performance is important.
  • Place the data and log files (.mdf and .idf) in separate logical drives and separate channels or controllers. 
  • Unless your Storage Area Network (SAN) is optimized for high I/O, stick a locally attached disk array.
  • Get disk controllers with battery backed-up write-back cache. The more the better, but at least 256 MB.
Last modified