Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Netflow Traffic Analyzer (NTA) > Migrate the NTA Flow Storage Database to another disk drive on the same server

Migrate the NTA Flow Storage Database to another disk drive on the same server

Last Updated: 6-7-2016 | Migration Guide

Supports: NTA 4.2 and later

This guide details how to migrate your NTA Flow Storage Database from the local disk to a new remote server. Due to the database size, historical data you will capture, and the activity of the server, we recommend installing the NTA Flow Storage Database  on a dedicated server or at least a dedicated disk or partition.

You may need to migrate if...

  • The database  shares a server with a poller or other products
  • The database is encountering performance and disk space issues
  • The requirements for the database have changed

The NTA Flow Storage Database Configurator includes a database backup option. We recommend using this option as part of your normal database and server maintenance.

If the NTA Flow Storage Database is not empty, and you are connecting it to an empty SQL Database, you must delete all data from the NTA Flow Storage Database. Otherwise, the existing data might be associated with wrong nodes and interfaces.

NTA Flow Storage Database requirements

These requirements are a guideline of minimum hardware and software requirements recommended for your database. You can also use a VM for the database, following the VM requirements for NPM installations.

Hardware/OS Requirements

Production environments require 4 CPUs (4-16 CPUs)

3 GHz or faster


Production environments require minimum 16GB (16-128GB)

To ensure optimal performance, we recommend increasing RAM together with the database size.

Hard Drive Space

20GB on 7200 rpm disk or more. NTFS file system required.

Recommended: Raid configurations of 0 or 1+0.

Other RAID and SAN configurations are not recommends and can result in data loss and decreased performance.

With the default 30-days retention period and default top talker optimization, you should plan at least 8GB of additional storage capacity per sustained 1000 flows per second. The required hard drive space strongly depends on your flow traffic.

OS 64-bit Windows Server 2008 or newer

Prepare your new server

Before backing up data, prep your local disk drive or partition for the migration. If you are migrating or upgrading products, you should plan that migration with your database migration.

1. Prep hardware for the migration

Prepare your local disk drive or partition. Review the minimum SolarWinds Orion platform requirements, multi-module guidelines, and specific product requirements (release notes and admin guide) for your product.

2. Gather credentials Gather the local admin credentials for the current and new server

Backup the NTA Flow Storage Database

Migrate the Flow Storage Database to another disk drive on the same server

When migrating the database to another folder on the same drive, you use an .exe file to migratethe content. You do not need to copy and paste the folder onto the other drive. The application completes the migration and configures the file path for you.

If you receive a message that the server does not have enough free space to migrate, you have a choice to cancel and free up space or start a partial migration. We recommend using a larger server or freeing up more space. A partial migration will not migrate your oldest flow data, and you may have issues storing new flow data.

1. Stop services Stop the SolarWinds NetFlow Service or the SolarWinds NetFlow Storage Service.
2. Locate and run the database move  .exe Locate and run the SolarWinds.NetFlow.FastBit.DbMove.exe in the folder where you have installed your NTA Flow Storage Database, such as C:\Program Files (x86)\SolarWinds\Orion\NetFlowTrafficAnalysis
3. Select the new folder location for the database Define the folder path to the new NTA Flow Storage Database location. This path should be on the new drive on the same server.
4. Move the database Click Move. The .exe moves the NTA Flow Storage Database to the new location on the same drive.
5. Enter the new file path

Start the NTA Flow Storage Configurator in the SolarWinds Orion > NetFlow Traffic Analysis program folder. Change data file path to the new destination folder for storing your flows data. Click OK.


6. Start services Start your services on the main Orion and additional polling servers.

Migrate flow data from the SolarWinds Orion SQL database to the Flow Storage Database

If you are upgrading to NTA 4.1 from a previous version that saved data to the SolarWinds Orion database, you should migrate this data to the NTA Flow Storage Database. This process starts as selected when upgrading NTA. For the migrated flows, you need approximately twice the space the flows currently take in the SQL database.

You should have the NTA Flow Storage Database installed prior to migrating.

The process runs in the background and can take extensive time and system resources to complete. We recommend letting the migration run without starting other processes.

You can check the progress of the migration any time through the Orion Web Console notification bar.

1. Back up your SQL database

Back up your SolarWinds Orion database. If you need help, please check your vendor's site for documentation and instructions.

If you have your database on a VM, create a snapshot or copy of your VM.

2. Run the Configuration Wizard Start the Configuration Wizard if it did not start or you skipped it as part of your NTA upgrade.
3. Select how to migrate historical data

You can select to:

  • Migrate historical data from previous installation: This option migrates your flow historical data.
  • Do not migrate my historical data: This option keeps the historical flow data in the SQL database. You can further select to:
    • Keep flow data in the Orion SQL database and migrate it later using the Configuration Wizard
    • Delete flow data from the Orion SQL database to permanently remove it.
4. Verify your backup Type in YES and continue. The Configuration Wizard checks if the Flow Storage Database server has enough space for the migration. If you need more space, a message displays. We recommend making space or installing the Flow Storage Database on a large server.
5. Review and migrate Review the selections and click Finish to start your migration. The process starts, running in the background.
6. Start services Start your services on the main and additional polling servers.

Learn more...


Last modified