Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA 4.2.3 Administrator Guide > NTA settings > Remote NTA Flow Storage Database covered by Microsoft Failover Cluster

Remote NTA Flow Storage Database covered by Microsoft Failover Cluster

To protect your flow data in a remote NTA Flow Storage Database, you can cover the database by the Microsoft Failover Cluster.

The failover system automatically assumes the primary server functions only in the following cases:

  • NTA Flow Storage Database stops
  • NTA Flow Storage Database server is down

Failover time

If spare servers in the Failover Cluster are up and running, it takes less than two minutes to failover on most environments. If the cluster needs to start a spare server to become active, you need to additionally count in the starting time of the server.

Some data loss can occur during failover due to service unavailability, when flows are waiting on the NTA receiving service.

On the figure, you can see a full high availability environment. This article deals with setting up the NTA Flow Storage Database to work with the Failover Cluster, which is highlighted in yellow in the picture.



  • Multiple Windows 2012 servers with similar hardware configuration in the same domain
  • SAN drive connected to all servers with:
    • NTFS format
    • Sufficient free space to store all flow data

Recommendations for the SAN drive

  • Use RAID 10 to gain performance and fault tolerance.
  • Use HA connection to avoid a single point of failure.

Set up NTA Flow Storage Database and the Failover Cluster

  1. Install the failover feature to appropriate servers.
  2. Set up the failover cluster. For more information, see the Microsoft Failover Cluster help.
  3. If you installed the Failover feature using an installer, the SAN disk is automatically taken by the Failover for quorum witness purposes. To use it as your data storage, free it with the Failover Management wizard:

    If you are using PowerShell for the installation, use the -NoStorage option to keep the SAN disk free.

    • Launch the Failover Management Wizard, selecting the following items: Failover Management > More Actions > Configure Cluster Quorum Settings > select Quorum > select Shared Folder, and click Finish.
  4. Install NTA Flow Storage Database on all servers.
    1. Install NTA Flow Storage Database on the server where the SAN disk is attached.
    2. In the Flow Storage Configurator, specify the folder for storing flow data to be located on the SAN storage.
    3. Power off the server and SAN disk.
    4. Repeat the previous steps (a-c) on all servers where the disk is attached. Always use the same folder for storing flow data.
  5. Power on all servers.
  6. Add the NTA Flow Storage Service monitoring using the Failover Management:
    1. Start the failover management and go to Configure role > Generic service.
    2. Select the SolarWinds NetFlow Storage Service from the list.
    3. Provide the access point information. It will be used later when connecting the SolarWinds NTA poller to this NTA Flow Storage Database.
    4. Select the SAN storage you already used for the service during the installation.
    5. Add the following items into the monitored registry:
      • Software\Wow6432Node\SolarWinds
      • Software\Wow6432Node\
    6. Confirm the settings and complete the procedure.
  7. Install SolarWinds NTA on the main Orion server and connect it to the access point, using the hostname or IP address, which you created in step 6c.
  8. Install additional SolarWinds NTA pollers.


Last modified