search cancel

Nimsoft Monitor Server Sizing and Scalability Notes


Article ID: 33909


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


Check the Nimsoft Monitor Server Installation Guide for Hardware Requirements and Recommendations for each given release at
For example:
The following recommendations below will change based on the version of Nimsoft being deployed as well as the size of the deployment.

Minimum requirements for different size deployments are included in the Nimsoft Server Installation guide. Hardware needs are determined by the size of your deployment, which is based on the number of hubs and robots you expect to install. When choosing your size, keep in mind that a hardware configuration that works today may need to grow in the future. Forecast growth when choosing your hardware. Use the numbers provided here to begin planning your deployment, but also consider that your particular situation may impose greater or lesser demands on the system.
Nimsoft Server (Primary Hub)

? Recommend 1 Primary AND 1 Secondary (Backup) Nimsoft Server for failover
? OS: Windows 2008 R2, 64-bit recommended.
? 2x Quad Core or higher
? Processor Speed: 3 GHz or higher
? RAM: 8 GB or higher preferred
? GB of Disk: 300 GB or higher
? Separate server
? 64-bit OS
? Tunnels: primary hub/server should act as Tunnel ?Client? for higher scalability.
Database Server

Separate 'physical' and dedicated machine is recommended.

? Microsoft SQL Server 2008 or higher
? 2x Quad Core or higher
? Processor Speed: 4 GHz or higher
? RAM: 8 GB RAM minimum, 12 GB or higher
? GB of Disk: Raid 10 disk system 300+ GB*
? Recommend SQL Server failover cluster*
? 64-bit OS/MS SQL Server
Recommended Disk configuration:

? RAID 10
? Transaction log on its own separate physical disk*
? OS on its own separate physical disk
? Database not on transaction log or OS disks
? 64-bit MS SQL Server
Note: Best-practice on SQL servers is to NOT to run anti-virus software.
We recommend that you separate the LDF (transaction log file) file from the MDF (data) file. If they are on the same drive, they contend for service. This slows down overall performance ? particularly for inserts and updates which is central to our operations.
We also recommend setting aside a minimum of 1TB of storage for the Nimsoft SLM database setup as multiple RAID stripped drives (either 2 500GB or 4 250GB).
Unified Monitoring Portal (UMP)

? 2x Quad Core or higher
? Separate server
? RAM: 8 GB RAM or higher
? 64-bit OS
***Faster disks and controllers (even multi-highspeed-controller) will make a huge difference in the Nimsoft SLM database performance which will translate over to UMP and primary hub performance.
Note that if you are using the UMP DMZ installation, this requires another box but usually doesn't requiring the same hardware resource as the UMP or SLM database server. It can be much more scaled down, but should have high-quality fast Network I/O performance.
?Simple? Hub

For a simple hub (not the Nimsoft Server) the minimum requirements are generally:
CPU: 2.66 GHz processor or better
Memory: 4 GB RAM or higher
Disk: 20 GB Disk minimum
As a thumb rule some field services personnel factor in 500 GB to 1 TB DB size for the Nimsoft DB as it tends to grow fast if you have lot of QOS being collected and stored in the database.? Depending on your data retention interval (configured in the data_engine probe), you can choose how long you need to retain the data. If this is up to 1 year then database maintenance should be performed more frequently so it doesn't take as long to complete.
The attached Database Sizing Guide can be used to estimate your database size requirements. Lastly, if this is for a production implementation for a significant size deployment ? we would suggest you consult with the Nimsoft Professional Services team for a more detailed discussion on architecture, scalability and sizing.

keywords: Nimsoft Monitor Server UMP Database sizing scalability NIS deployment size scaling disk storage requirements requirement environment guide guidelines best practices recommendation recommendations deployment hub robot robots version docs documentation hardware primary small medium large
question questions


Component: CAUIM