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

Migrating Orion to VM servers - Need some advice on server sizing

I'm in the process of migrating physical servers to VMs, and with my Orion setup I'm assuming things might be better if split up onto multiple VM servers. Can anyone give me some ideas of what applications should be separated into their own VMs, and how I should size those?

I currently have the below Solarwinds products installed on a single HP server with a 2.4Ghz processor and 36Gb of RAM:

Network Performance Monitor

Network Configuration Manager

Server & Application Monitor

IP Address Manager

VOIP and Network Quality Manager

Database Performance Analyzer

Netflow Traffic Analyzer

Patch Manager

Web Helpdesk

I know I should put the database on its own VM, but are the rest of the apps okay to be installed together, or should any others be separate as well? I currently have an SL500 license for NPM but will most likely be bumping up to SL2000 within the next 12 months, the actual amount of monitored nodes will most likely be around 1000.

Would a quad core server with 8Gb of RAM be enough for the application servers, or is that more of a minimum spec? How should the SQL server be sized? Should Web Helpdesk be on its own VM?

Thanks!

Find more posts tagged with

Accepted answers

All comments

cjfranca

You can use the same conf. the physical machine, but the database serve it is better to let the physical machine (NOT using raid 5) and create another for the NTA DB.
The server processor try to use one that has latest technology, the one u mentioned will not help, The WHD can rather be on a separate VM.

See more information here. Library & Support

GoldTipu

The following is a SAMPLE MINIMUM recommendation so you can add or subtract these according to your own needs.

Hardware Recommendations for Orion Servers
> NPM SLX /NCM DLX /IPSLA 25 Server
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8GB

http://ark.intel.com/products/52276/Intel-Xeon-Processor-E3-1270-8M-Cache-3_40-GHz

> NPM SLX /NCM DLX Server
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8GB

> NPM SLX Server
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8GB

> Each Additional Polling Engine Server
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8GB

Hardware Recommendations for SQL Servers
>SQL DB for NPM SLX /NCM DLX /IPSLA 25 Server/10 x APE
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8-12GB
Mirrored drives for OS and 6 disks Raid 1+0 for database data files

>SQL DB for NPM SLX /NCM DLX Server/10 x APE
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8-12GB

>SQL DB for NPM SLX Server/10 x APE
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8-12GB

**SQL Server Hardware Recommendation**

3 GHz, dual core processor or better. This will work for all size licenses. Do not use
less than a 2 GHz processor for any Orion SQL server.

Best Practice use RAID 10
2 x Raid 1 disk (Mirroring) For operating system
2 x Raid 1 disk (Mirroring) Place pagefile here and also can be used for applications and ad hoc Stuff
4 x RAID 1 +0 Stripping and mirroring for database files (2 partitions 1 for Data File and 1 for Log File)