"Bueller? ...Bueller? ...Bueller?"
Magic 8-Ball says...200 GB any comments?
A couple of things here to keep in mind.
- Netflow has its own set of retention settings. Go tou NetFlow Settings from the NTA Summary page to set.
- NetFlow will be the lion's share of the data , as you say. I would think about allocating 300-400GB to have room for growth.
- SQL for NTA running on a VM is not supported. SQL for NTA must be on a dedicated SQL server.
- We recommend locally attached storage with RAID 10 and 15 K spindles.
- See The specified item was not found..
That caveat about a dedicated physical box for SQL is not mentioned on the site. Where the following quote comes from.
Operating System Windows 2003 Server (32-bit or 64-bit) including R2, with IIS installed, running in 32-bit mode
Windows 2008 Server (32-bit or 64-bit) with IIS installed, running in 32-bit mode
.Net Framework Version 3.5 or later Database SQL Server 2005 SP1 Express, Standard, or Enterprise
SQL Server 2008 Express, Standard, or Enterprise
I seem to recall multiple posts referring to NPM/NTA running on virtual servers on these forums.
Little clarification please.
Upon further digging I did find a mention of this. Still though, it is unclear why this is the recommendation, please clarify if possible.
Running NPM and NTA on a virtual server is OK. SQL does not perform well for high I/O applications such as NTA when installed on a virtual server. That is why we don't support SQL on VM's. In the past, we have seen a lot of implementations with SQL on a VM and it has a very negative impact on NTA performance.
BTW, 5 Months later our database is only about 20 Gigs. So size seems to be pretty small despite cranking all the settings up and adding more nodes.
We're also running the poller and the DB on separate virtual servers. Runs along perfectly, if a little CPU hungry.