Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > Migrate the NTA Flow Storage Database from a remote server to the local disk

Migrate the NTA Flow Storage Database from a remote server to the local disk

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 a remote server to the local disk. 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
CPU

Production environments require 4 CPUs (4-16 CPUs)

3 GHz or faster

RAM

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

Prior to moving the database, you should locate the database and create a backup.

The NTA Flow Storage Database is not an SQL database. You can perform backups creating copies of the folder or using the NTA Flow Storage Database Backup Scheduler. For this example, we copy and paste the folder to an external drive or USB.

1. Open the NTA Flow Storage Database Configurator Start the NTA Flow Storage Database Configurator in the SolarWinds Orion > NetFlow Traffic Analysis program folder.
2. Locate the database file path You will find the path to the current NTA Flow Storage Database destination folder in the NTA Flow Storage Database data file path field. Click Cancel to close the Configurator.
3. Backup the database

Backup the database by copying and pasting the database folder to another server or external drive. If you have a backup folder entered, you can backup to this location.

Migrate the Flow Storage Database from a remote server to local disk

You can migrate the database between servers by backing up and restoring the database on a different server. After it is migrated, you need to configure and update all configurations to point to the new location.

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. Log in to the NTA server Log in to the server where your NTA Flow Storage Database is currently installed.
2. Stop the NetFlow service Stop the SolarWinds NetFlow Service.

3. Go to your NTA Flow Storage Database folder

Locate your NTA Flow Storage Database folder in a file explorer.

4. Copy the database folder to the new server

Move the NTA Flow Storage Database folder with its contents to the target server using standard Windows tools (Copy & Paste, shared folder, or FTP).

5. Install the NTA Flow Storage Database

 Run the NTA installation file and select the NTA Flow Storage Database option.

6. Update NTA on the main polling engine

You need to update the main server NTA with the new location of the database:

  1. Log in to the NTA server and run the NTA executable.
  2. For the configuration option, select NPM/NTA/NTA Flow Storage Database on two separate servers and click Next.
  3. Move through the following screens to review the Welcome information and accept the terms of the license agreement.
  4. Click Change and complete the Setup Wizard.
  5. Select the appropriate licensing option.
  6. Reconfigure your NTA using the Configuration Wizard. When prompted for the location of the NTA Flow Storage Database, enter the location on the local server where you migrated the data.
7. Uninstall the NTA Flow Storage Database from the remote server (Optional) (Optional) Log in to the original remote server with the NTA Flow Storage Database. Uninstall the database from the remote server.

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

Tags

Classifications

Public