Could Someone tell me about an experience of running NMS on virtual machines and how did you size these machines?
We plan to move to VMware machines DB and APP
Our environment is about 95% virtual, with only a few End to End servers and our database server being physical. I'm not sure how the database would perform on virtual, but we most likely wouldn't do this. Our setup is as follows:
Nimsoft Virtual Servers
CPU: 2.4 GHz
Memory: 2048 MB
DISK:C -15 GBE -39 GB
OS: Windows Server 2003
Nimsoft Database Server
CPU: 8 Core 2.8 GHz
Memory: 32765 MB
DISK: C –70 GB (OS)E –205 GB (Local Disk)F –850 GB (Data)I –100 GB (Index)L –100 GB (Log)T –25 GB (Temp DB)
OS: Windows 2008 64-bit
I've not noticed any performance issues, however we've added to our primary HUB's resources a few times. Currently we are maxed on memory at 4 GIG and have it setup with 2 CPU's, running at the same speed.
I could answer to every questions you have about this topic! Because I thinks i have faced off every issue possible on this kind of architecture!
At the beginning, I installed only one hub on a VM. Web interface (UMP - wasp probe) and DB (SQL 2008)were installed on the same server.
Everything seemed to work find until I reach approximatively 30 monitored machine. After that, my HUB has show some lack of performance. So I have added ressources to the VM. Due to "default" configuration of SQL server, sql process takes as much memory it coulds, so quickly I faced off lake of perf again. So Ifixed the max memory used by SQL server to half of Memory.
Again, everythings seemed OK until I increased the number of monitored machine. At this step, UMP has begun to deiplay error message and interface has begun to be slow. So thanks to Nimsoft support I decided to add a new NMS server, dedicated to UMP (wasp probe).
after a while, a new lack of perf has appeared... and after investigation, It was due to I/O perf from SQL... because a lot of probes have been deployed to monitored machines. And finaly I moved the SQL server easily with Nimsoft support to a Phisycal server.
and now it makes almost 3 months that my NMS achitecture is stable.
so from a single server I have moved to a 1 Hub server + 1 Ump server + 1 db dedicated server.
I hope it will help you....
Ssuk is right on the nose with the VM setup. The only difference between what he did with the SQL database and what we did was we left SQL as a Virtual Machine and just attached physical disks to the VM. The bottle neck that we seen was always with the disk I/O when you have a lot of QoS data being pushed to the database.
Very useful information people thank you. I have all the following as VM's, primary hub, tunnel server hub, UMP and SQL Database. Recently (after adding a lot of probes and QOS data collection) I have seen very slow I/O to the database even with large amounts of disk available. I will now look at physical disk or physical server.
On the primary, tunnel server and UMP I use 64bit Vm's and 4GB ram and they have worked okay but I guess it is down to the size of the environment they support.
Retrieving data ...