Documentation forSolarWinds Observability SaaS

Configure deployed Network Collector for High Availability installation

By default, the Network Collector uses an embedded SQL Server Express to store configuration and temporary data.

To set up High Availability for Network Collector, you need to migrate the database to a separate SQL Server. Both the active and backup Network Collectors use this SQL Server to share configuration and temporary data.

Migrating allows you to keep all relevant configurations. Historical data are not fully preserved, and this is not needed as the metrics, topology data, flows, and other historical data are persisted in the cloud.

SolarWinds provides High Availability on the application level. It is the customer’s responsibility to provide High Availability for the SQL Server.

High Availability requirements

Requirement type Details
Network Collector version 2024.1 or later
Server software

A separate MS SQL Server 2022

For fresh installations, the Network Collector also supports older versions of SQL Server. The full list of supported SQL versions is:

  • SQL Server 2022 (including installations on Linux)
  • SQL Server 2019 (including installations on Linux)
  • SQL Server 2017 (including installations on Linux)
  • SQL Server 2016 SP1 or SP2

Recommendations

  • Use Standard or Enterprise editions of SQL Server 2022 (including installations on Linux).

    The Express edition is also supported for the production environment but does not provide the Always On availability groups feature. For the upgrade, only SQL Server 2022 or newer is supported because SQL Server Express 2022 is embedded.

  • Support for Microsoft SQL Server Service Packs and Cumulative Updates is assumed unless otherwise noted.

Migrate the embedded SQL version to a new database server

  1. Prepare your new database server.

    Build the new database server including any changes to the architecture, hardware, and operating system.

  2. Stop Network Collector services.

    On the server where Network Collector is installed, open the SolarWinds Platform Service Manager application and stop all SolarWinds services.

    • SolarWinds recommends discussing database migrations with a DBA. You should also schedule a maintenance window to migrate, during non-peak hours (recommended), and notify your company when taking services offline to migrate.

    • When you migrate your database, your services are down and not collecting polling data.

  3. Back up the SQL database. On the machine where Network Collector is installed, run the SQL Server Management Studio (SSMS) and back up the following databases:

    • SolarWindsOrion
    • SolarWindsOrionLog
    • SolarWindsFlowStorage

    See the Microsoft article Create a Full Database Backup for details.

    If you do not have SSMS installed on the Network Collector server, use the following link to download SQL Management Studio: https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver16.

  4. Restore the database to the new server. Copy and restore the database to the new server, for example using the SQL Management Studio.

  5. On the Network Collector, run the Configuration Wizard to update the database connections. Perform the following steps:

    1. Run the Configuration Wizard to update the database location.

    2. On Database Settings, specify your new database server in the SQL Server field.

    3. Select the user with sufficient rights to the migrated database (db_owner) or select a user with privileges to create a new user. Click Next to continue. See SQL permission role requirements on the SolarWinds Platform.

    4. Select Use an Existing Database and select or type the database name and click Next. When prompted to use the existing database, click Yes.

    5. On Database account, specify the account for accessing the database. Select an existing account or create a new one.

      SolarWinds recommends that you create a new account to ensure that the SolarWinds Platform has required access to the database:

      1. Select Create a New Account and provide a New Account name.

      2. Provide and confirm an account Password and click Next.

    6. Complete the wizard.

  6. Start services. Using the SolarWinds Platform Service Manager, start all services on the Network Collector.

The Network Collector uses the new database on a separate server and is ready for the installation of the High Availability backup server.

Set up High Availability for an already deployed Network Collector

  1. Log in to the Network Collector server which you want to use as a backup server.

  2. Download the Network Collector installer to the server.

    Adjust the following download URL according to your region. Replace xx-yy in the URL with your data center. See Find the data center and endpoints for your organization.

    https://downloads.solarwinds.com/solarwinds/Observability/RTM/Solarwinds.Observability.NetworkCollector.OfflineInstaller_SOC_SWOURL=xx-yy.cloud.solarwinds.com.iso
    Endpoint Replace xx-yy with SOC_SWOURL
    AWS NA region dc-01 dc-01.cloud.solarwinds.com.iso
    Azure NA region dc-02 dc-02.cloud.solarwinds.com.iso
    AWS EU region dc-03 dc-03.cloud.solarwinds.com.iso
    AWS Australia region dc-05 dc-05.cloud.solarwinds.com.iso

  3. Mount the ISO file and run the installation file on the server.

  4. In Installation Type, select High Availability for an existing collector.

  5. On Server Connect, provide the IP address or host name of your primary Network Collector server, your user name and password.

  6. Paste the API token and complete the installation wizard. For details on completing the installation, see Network Collector.

In case of failover, your Network Collector will switch to the secondary server in the pool. To see details about your High Availability setup in SolarWinds Observability, click Settings > High Availability.

Set up High Availability with your Network Collector concurrently

Use the following instructions for your deployment when a Network Collector is getting deployed in High Availability on day one.

Install Network Collector on the primary server

  1. Prepare the Ingestion token in SolarWinds Observability SaaS.

    In SolarWinds Observability SaaS, go to Settings > API Tokens and click Create API Token. Copy the token into clipboard.

  2. Download the Network Collector installer to the server.

    Adjust the following download URL according to your region. Replace xx-yy in the URL with your data center. See Find the data center and endpoints for your organization.

    https://downloads.solarwinds.com/solarwinds/Observability/RTM/Solarwinds.Observability.NetworkCollector.OfflineInstaller_SOC_SWOURL=xx-yy.cloud.solarwinds.com.iso
    Endpoint Replace xx-yy with SOC_SWOURL
    AWS NA region dc-01 dc-01.cloud.solarwinds.com.iso
    Azure NA region dc-02 dc-02.cloud.solarwinds.com.iso
    AWS EU region dc-03 dc-03.cloud.solarwinds.com.iso
    AWS Australia region dc-05 dc-05.cloud.solarwinds.com.iso

  3. Unblock the ISO file if necessary.

  4. Mount the ISO on the server, and start the installation.

    1. Installation Type: Select Collector, then click Next.

    2. Access Token: In the field for API Token, enter the token you created.

    3. License Agreement: Agree to the license agreement, and click Next.

    4. Installation Options:

      1. Select which SQL Server to use:

        • Select Use SQL Server if you have a dedicated SQL Server 2016 SP1 or later.

        • Select Install SQL Server Express to deploy a local database.

          Use this option for lightweight installations. SQL Server Express has database size limits, such as 50 GB for SQL Server Express 2025. If you need a larger database later, you will have to migrate the database to a SQL Server Standard or Enterprise.

      2. Select the Destination folder where the Network Collector will be installed.

      3. Click Next.

    5. Installation Report:

      1. Review the system check results and address any issues.

      2. Click Install.

  5. Configuration Wizard:

    1. Install all missing IIS components.

    2. Click Yes.

  6. SolarWinds Configuration Wizard:

    1. In the welcome screen, click Next.

    2. Database Settings: Configure the main database for storing configuration and performance data.

      1. SQL Server - Enter tcp:hostname,port for your SQL Server (for example, tcp:yourserver,1433).

      2. SQL Server credentials and connection configuration - Use sa level credentials, and click Next.

      3. Create a new database - This is the main SolarWindsOrion database. Click Next.

      4. Create a new account - This account is tailored for optimal SolarWinds Network Collector operations. Click Next.

    3. Website Settings: Define the website configuration and click Next. This is the local Network Collector web console.

    4. Database Settings for Log and Events Monitoring: Configure the database for storing logs and events data.

      1. Place log and event database on a dedicated SQL Server. Click Next.

      2. SQL Server - Enter the tcp:hostname,port (for example, tcp:yourserver,1433).

      3. SQL Server credentials and connection configuration - Use sa level credentials, and click Next.

      4. Create a new database and click Next.

      5. Create a new account - This account is tailored for optimal SolarWinds Network Collector operations. Click Next.

    5. NTA Flow Storage Configuration: Configure the database for storing flow data.

      1. SQL Server - Enter the tcp:hostname,port (for example, tcp:yourserver,1433).

      2. SQL Server credentials and connection configuration - Use sa level credentials, and click Next.

      3. Create a new database and click Next.

      4. Create a new account - This account is tailored for optimal SolarWinds Network Collector operations. Click Next.

    6. Completing Configuration Wizard - Click Next.

    7. Configuring SolarWinds Platform - Click Finish.

    8. Log in to the local Network Collector web console (configured in website settings) and configure the password for Admin account.

Deploy Network Collector on the backup server

  1. Download the Network Collector installer to the server.

    Adjust the following download URL according to your region. Replace xx-yy in the URL with your data center. See Find the data center and endpoints for your organization.

    https://downloads.solarwinds.com/solarwinds/Observability/RTM/Solarwinds.Observability.NetworkCollector.OfflineInstaller_SOC_SWOURL=xx-yy.cloud.solarwinds.com.iso
    Endpoint Replace xx-yy with SOC_SWOURL
    AWS NA region dc-01 dc-01.cloud.solarwinds.com.iso
    Azure NA region dc-02 dc-02.cloud.solarwinds.com.iso
    AWS EU region dc-03 dc-03.cloud.solarwinds.com.iso
    AWS Australia region dc-05 dc-05.cloud.solarwinds.com.iso

  2. Unblock the ISO file if necessary.

  3. Mount the ISO on the second server, and start the installation.

    1. Installation Type: Select High Availability for an existing collector, and click Next.

    2. Server Connect:

      1. Enter the IP or hostname of the primary Network Collector server.

      2. Username: Enter Admin.

      3. Password: Use the Admin Password configured during the first login into the primary Network Collector web console.

    3. Access Token: In the field for API Token enter the token created in the SolarWinds Observability Self-Hosted and click Next.

    4. License Agreement: Agree to the license agreement, and click Next.

    5. Installation Options: Select the Destination folder where the Network Collector will be installed, and click Next.

    6. Installation Report:

      1. System confirmation and check.

      2. Click Install.

  4. Configuration Wizard:

    1. Install all missing IIS components.

    2. Click Yes.

  5. SolarWinds Configuration Wizard:

    1. In the welcome screen, click Next.

    2. Database Settings:

      1. SQL Server - Enter the tcp:hostname,port (example: tcp:yourserver,1433).

      2. SQL Server credentials and connection configuration - Enter sa level credentials, and click Next.

      3. Use the database you configured on the primary Network Collector server and click Next.

      4. Use the account you configured on the primary Network Collector server, then click Next.

    3. Website Settings:

      1. Define the website configuration - This is for Network Collector local web console. Click Next.

    4. Database Settings for Log and Events Monitoring:

      1. Place log and event database on a dedicated SQL Server, and click Next.

      2. SQL Server - Enter the tcp:hostname,port (for example, tcp:yourserver,1433).

      3. SQL Server credentials and connection configuration - Use sa level credentials, then click Next.

      4. Use the logs database you configured on the primary Network Collector server and click Next.

      5. Use the logs database account you configured on the primary Network Collector server, then click Next.

    5. NTA Flow Storage Configuration

      1. SQL Server - Enter the tcp:hostname,port (example: tcp:yourserver,1433).

      2. SQL Server credentials and connection configuration - Use sa level credentials, and click Next.

      3. Use the NTA Flow Storage database you configured on the primary Network Collector server and click Next.

      4. Use the NTA Flow Storage account you configured on the primary Network Collector server, then click Next.

    6. Completing Configuration Wizard - Click Next.

    7. Configuring SolarWinds Platform - Click Finish.

Set up a High Availability Pool

A High Availability (HA) pool is a group of two servers that have access to the same network and database resources. The pool includes one main server and one secondary server. Each server is called a pool member and can take over all responsibilities of the other server.

When a pool member is sending and receiving data, it is the active pool member. When a pool member is waiting to take over, it is the standby pool member.

If you use a virtual hostname, the browser and computer may cache the host name of the active server. If you are testing using the host names, you may need to flush your DNS cache.

Before you begin, you need the following:

  • A VIP address (for single subnet installations)
  • A virtual hostname (for multiple subnet installations)
  • A secondary HA server
  • The software automatically detects if you are installing on a single subnet or multiple subnets.
  • Virtual hostnames cannot use punctuation.

Single subnet

  1. In the Network Collector web console, click Settings > My Deployment.

  2. Activate the Servers tab and click Setup High Availability pool next to your standby server.

  3. Choose the server you want to make highly available.

  4. Enter the pool name.

  5. Enter your VIP. On single subnets, providing the VIP is obligatory.

    The VIP must be unassigned and on the same subnet as the primary and secondary servers.

    You can use both VIP and virtual hostname at the same time. If you use a virtual hostname, do not include the domain name.

  6. Click Next, and review your selections.

  7. Click Create Pool to complete the pool setup.

Your main server is now highly available and can failover to the standby server on the same subnet. An audit event is logged when you create the pool.

When the pool is created, the High Availability Deployment Summary displays the active and standby servers grouped under the pool name. In SolarWinds Observability SaaS, you can find the information under Settings > High Availability > Pools.

You may need to refresh the page to see the correct pool and server status.

SolarWinds recommends that you perform a manual failover after you create your pool and observe the data collected to ensure that all network and device changes are correct.

Multi-subnet

The servers must be able to resolve the host name of the other server in the pool. You may need to update the hosts file on each server.

  1. In the Network Collector web console, click Settings > My Deployment.

  2. Activate the Servers tab and click Setup High Availability pool next to your standby server.

  3. Choose the server you want to make highly available.

  4. Enter the pool name and the virtual hostname. Do not include the domain name in the virtual hostname.

    You must provide a virtual hostname. Virtual IPs are not supported for multi-subnet deployments.

  5. Click Next.

  6. Select the DNS type.

    • Microsoft DNS

      1. Enter the IP address of the DNS server that manages the pool members' DNS Zone.

      2. Enter the DNS Zone.

      3. Enter administrative credentials for the DNS server.

        We recommend a local administrator account configured for WMI access. For non-local administrator accounts, we recommend an administrator account with full DACL and remote WMI management enabled.

    • BIND DNS

      The BIND server must allow the virtual hostname to update dynamically. The operating system must also allow for dynamic updates to the DNS.

      1. Enter the IP address of the DNS server that manages the pool members' DNS Zone.

      2. Enter the DNS Zone.

      3. Enter the TSIG secret key name and the TSIG shared secret key value.

    • Other

      • Use this option if you can use scripts to update the DNS entry for the host name.
      • SolarWinds cannot validate the DNS server IP address or DNS zone for this selection.

      1. Enter the IP address of the DNS server that manages the pool members' DNS Zone.

      2. Enter the DNS Zone.

  7. Click Test to validate your Microsoft or BIND credentials and permissions.

  8. Click Next to complete the pool setup. The software validates the virtual hostname against the selected DNS server. If the host entry already exists, you are prompted to overwrite the entry or change the virtual hostname.

Your main server or additional polling engine is now highly available and can failover to the standby server across subnets. An audit event is logged when you create the pool and the DNS entry points to the active server.

When the pool is created, the High Availability Deployment Summary displays the active and standby servers grouped under the pool name. In SolarWinds Observability SaaS, you can find the information under Settings > High Availability > Pools.

SolarWinds recommends that you perform a manual failover after you create your pool and observe the data collected to ensure that all network and device changes are correct.

  • You may need to refresh the page to see the correct pool and server status.

  • You may set the DNS Time to Live of your virtual hostname record in your script. SolarWinds recommends setting your DNS Time to Live to a shorter time period, such as a minute. You may also need to flush your browser's DNS cache by closing and reopening your browser after manual switchover.

Disable or enable HA pools

During upgrade or maintenance on your High Availability (HA) pool members, you must disable your pool. HA pools can also be disabled when you no longer have sufficient HA pool licenses for the number of enabled pools.

  1. In the Network Collector web console, click Settings > My Deployment.

  2. Activate the Pools tab and select the pool you want to disable/enable.

  3. Change the pool status:

    • To disable an active pool, click Disable.

    • To enable an inactive pool, click Enable.

The pool status changes according to your settings.