We will be using NPM to monitor approximately 1500 elements; what will be the approximate disk space required for the database. Can we install the database on the same machine (VM) as NPM or does this have to be a separate machine.
I would strongly suggest that you run SQL on a seperate, dedicated box, with above average IO capabilities. We have over 4000 elements and retain our daily statistics for 2 years and our database is about 20.8 GB.
Like the previous poster said, it totally depends on polling frequencies & data/statistics retention. By the way, we are running NPM, NCM & APM all on a single VM and it works fine. The SQL box is physical, but with the right storage back-end you could do SQL on a seperate VM as well.
It's a "how long's a piece of string?" type of question. So much depends on how you deploy. With all the standard settings, you could easily get away with change from 10GB, but the moment that you change polling frequency or retention time, you affect the size. If you poll twice as often, you have twice as much data and if you also retain it for twice as long, you have four times as much data. You need to just try & keep your SQL volumes tracked too. SQL will need housekeeping as normal and you may notice that some tables (like traps) grow faster than you'd expect (or want) so you can then tailor the product to fit your business.You'd be better off running the SQL on a separate physical server because SQL would take a huge lump out of an ESX host anyway.
I will second DirtySouth's response--we definitely recommend that you run SQL on a seperate box. For more information, please see the NPM Requirements section of the Orion NPM Administrator Guide. Use the arrow keys to scroll through the document.
M
Thanks mate... that answers my query for now.
