This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

NTA Flow Storage Database Capacity

How much space (Both Cloud and Physical) is recommended for NTA Flow storage Database if client want 6 month of retention?
As per Solarwinds for 30 days retention it is recommended to have System SSD 320 GB (included in D12_v2) + Data Azure Storage Disk Volume 2.5 TB (2.5 TB is Flow Storage, 300k FPS with 30-days retention, Azure Storage Disk with Provisioned IOPS recommended) for SLX and for medium it is System SSD 80 GB (included in D12_v2) + Data Azure Storage Disk Volume 500 GB (8 GB for every received sustained 1000 Flows/s with 30-days retention period).

Please help.

  • Do you have NTA currently installed and working. If yes please try the link Success Center

  • Pushkar,

    You've located the correct document for system requirements for the latest version of NTA - that's here: NetFlow Traffic Analyzer 4.6 System Requirements

    That recommendation is a general rule of thumb for planning: 8G for every sustained 1000 fps, for a 30 day retention period. The NTA flow database stores granular data over the entire retention period; there's no aggregation or summarization.  So - the storage requirements scale linearly over the retention period.

    For example, if you are receiving 10,000 flows per second, you would need (10000/1000)*8GB = 80GB for 30 days retention. Multiple by six to get approximately 480GB for six months retention.

    I say approximately because this is only a rule of thumb. There are many factors which are specific to your environment that influence the actual storage you'll need.  It's not possible to perfectly predict your flow storage requirements in advance, and this is an important point to understand.

    Some of the factors that influence your actual storage requirements include: The actual flow rates over time, and burstiness or variability of flow traffic, the number of flow sources, the number of interfaces monitored,  the diversity of the endpoints represented in the flow records, how you handle DNS resolution, and the value for Top Talker optimization.

    Use this rule of thumb for planning only. Give yourself a buffer; storage is relatively inexpensive. Monitor your database size over time, and adjust accordingly.

    jreves