Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Storage Resource Monitor (SRM) > SRM Installation Guide > Plan your production deployment

Plan your production deployment

Created by Nigel, last modified by Nigel on Mar 14, 2017

Views: 75 Votes: 0 Revisions: 1

Before you install SolarWinds SRM in a production environment, size your environment to ensure that the system has enough capability to meet your monitoring needs.

If you are installing an evaluation copy of SRM, see Install an evaluation copy of SolarWinds SRM.

Server sizing depends on:

  • Number of monitored storage objects: an object can be a storage array, storage pool, LUN, volume, Vserver, or file share
  • Polling frequency: SolarWinds SRM regularly polls devices to collect data and determine status. If you decide to collect performance statistics more often than the default 15 minutes, system requirements increase
  • Number of simultaneous users: Add 1 GB of RAM for every 25 simultaneous users

Requirements

Use the following table to size your SolarWinds SRM environment:

Size of deployment Monitored Environment Windows Application Server
(physical or virtual)
Microsoft® database server
(physical recommended)
Additional Polling
Engines
Small

5 Arrays
2,000 Disks
5,000 LUNs

Dual Core Processor 2.5 GHz or better; 8 GB RAM

2 x 146 GB 15K Hard Drives (RAID 1/Mirrored Settings)

1 GBE NIC

Microsoft® Windows Server® 2016, Microsoft® Windows Server® 2012, Microsoft® Windows Server® 2012 R2, Microsoft® Windows Server 2008 R2 SP1, with IIS in 32-bit mode*

NET 4.5.1*

Dual Core processor 3 GHz or better; 8 GB memory

2 x 146 GB 15K Hard Drives (RAID 1/Mirrored Settings)

Microsoft® Windows Server® 2016, Microsoft® Windows Server® 2012 or Microsoft® Windows Server® 2008 R2

Microsoft SQL Server 2016, 2014, 2014 SP1, 2012, or 2008 R2 Standard Edition

Optimal when running the Orion Platform database and logs in a hard drive configuration that supports Raid 1+0

Not required
Medium 25 Arrays
5,000 Disks
20,000 LUNs

Dual Core Processor 2.5 GHz or better; 8 GB RAM

2 x 146 GB 15K Hard Drives (RAID 1/Mirrored Settings)

1 GBE NIC

Microsoft® Windows Server® 2016, Microsoft® Windows Server® 2012, Microsoft® Windows Server® 2012 R2, Microsoft® Windows Server 2008 R2 SP1, with IIS in 32-bit mode*

NET 4.5 SP1*

Quad Core processor 3 GHz or better; 8 GB memory

2 x 146 GB 15K Hard Drives (RAID 1/Mirrored Settings)

Microsoft® Windows Server® 2016, Microsoft® Windows Server® 2012 or Microsoft® Windows Server® 2008 R2

Microsoft SQL Server 2016, 2014, 2014 SP1, 2012, or 2008 R2 Standard Edition

Optimal when running the Orion Platform database and logs in a hard drive configuration that supports Raid 1+0

1**
Large 50 Arrays
30,000 Disks
60,000 LUNs

Dual Core Processor 2.5 GHz or better; 8 GB RAM

2 x 146 GB 15K Hard Drives (RAID 1/Mirrored Settings)

1 GBE NIC

Microsoft® Windows Server® 2016, Microsoft® Windows Server® 2012, Microsoft® Windows Server® 2012 R2, Microsoft® Windows Server 2008 R2 SP1, with IIS in 32-bit mode*

NET 4.5.1 SP1*

Dual Quad Core processor 3 GHz or better; 8 GB memory

2 x 146 GB 15K Hard Drives (RAID 1/Mirrored Settings)

Microsoft® Windows Server® 2016, Microsoft® Windows Server® 2012 or Microsoft® Windows Server® 2008 R2

Microsoft SQL Server 2016, 2014, 2014 SP1, 2012, or 2008 R2 Standard Edition

Optimal when running the Orion Platform database and logs in a hard drive configuration that supports Raid 1+0

3**

* If the server does not have IIS or .NET installed, the installation automatically installs and configures these components for you. If the server has Internet access, use the online version of the installation. If not, use the offline version.

** Each additional polling engine requires the same requirements as listed in the Windows Application Server (physical or virtual) column.

FIPS support

Federal Information Processing Standard (FIPS) defines security and interoperability standards for computers used by the U.S. Federal Government.

SRM is FIPS 140-2 compliant. For instructions, see Enable FIPS.

Virtual machine and application server requirements

Orion application server installations on VMware™ or Microsoft hosted virtual machines are supported. The virtual machine requirements are identical to the physical server requirements.

 
Last modified
10:12, 14 Mar 2017

Tags

Classifications

Public