Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Move the NTA Flow Storage database to a different SQL server

Move the NTA Flow Storage database to a different SQL server

Updated August 16, 2018

Overview

This article provides information on changing the deployment type of the NTA Flow Storage database running on SQL server.

Environment

  • NTA 4.4 and later
  • SQL Flow Storage database

Details

SolarWinds supports two types of deployment for the NTA Flow Storage database:

  • Orion database and the Flow Storage database on one SQL server (recommended)
    • For this option, you must use SQL Server 2016 SP1 or later
    • This is a default deployment with SQL Server 2016 SP1 Express during express / evaluation / lightweight installation. You should consider changing the SQL server edition from Express to a higher one.
  • Orion database and NTA Flow Storage database on different SQL server instances:
    • Orion database running on a SQL Server 2012 or later instance.
    • NTA Flow Storage database running on a SQL Server 2016 SP1 or later instance.

Steps

  1. Prepare the SQL server.

    NTA 4.4 and later requires SQL Server 2016 SP1 or later for the NTA Flow Storage database.

  2. Stop all Orion services.

    This ensures that there will not be changes in any NTA data in Orion or Flow Storage databases.

  3. Back up the Flow Storage database and the Orion database.

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

    Using SQL Management Studio, do the following:

    1. Open the SQL Management Studio on the NTA Flow Storage database SQL server using your Windows credentials.
    2. From the Object explorer, expand Databases and locate the Flow Storage database.
    3. Right-click on the Orion database > Tasks > Backup.
    4. Create a backup of your NTA Flow Storage database.
  4. Restore the Flow Storage database on the new server.

    Using SQL Management Studio, do the following:

    1. Open SQL Management Studio on the new SQL server and connect using your SQL administrator account.
    2. In the Object browser, right-click Database, and click Restore Database.
    3. Locate the NTA Flow Storage database backup file, and click OK.
  5. Run the Configuration wizard on all Orion polling engines.

    This stops all Orion services.

  6. In the NTA Flow Storage Configuration dialogs, specify the new location of the Flow Storage database. Leave other settings as they are.

    cw-nta_flow_storage_configuration.png

  7. Complete the Configuration wizard.
  8. Start Orion services on all polling engines.

 

 

Last modified

Tags

Classifications

Public