SolarWinds Platform Active/Active installation is a deployment option that provides you with a duplicate of your SolarWinds installation for disaster recovery purposes. This deployment option is suitable only under special circumstances: it requires a special license and you need to regularly synchronize primary and secondary databases.

The SolarWinds Platform Active/Active solution is not suitable for customers who have deployed SolarWinds High Availability.

Download as PDF

Contents

• Prepare a SolarWinds Platform Active/Active installation
• Set up the Active/Active deployment
• Prepare a separate database
• Synchronize the SolarWinds Platform Active/Active environment for maintenance
• Handle passive monitoring (NetFlow, Syslog, and SNMP Traps)

Prepare a SolarWinds Platform Active/Active installation 

Limitations 

• The agents deployed in the network and connected to the primary server do not reconnect to the secondary server in the event of a primary outage (this is supported in HA solution).
• The traps, syslogs, NetFlow traffic, and the majority of the data that the device-initiated communication (VNQM Avaya, and so on) collects are going to the configured destinations. Some devices support multiple recipients. See the section "Handle passive monitoring (NetFlow, Syslog, and SNMP Traps) for Active/Active deployments". 
• If you limit devices to accept the traffic just from certain IPs, both the primary and secondary server must be on the device white list.
• Alerts and Alert actions, such as email messages, are duplicated and triggered from both primary and secondary SolarWinds Platform servers.
• Actions that access external files (for example, scripts) do not work unless you synchronize the files.
• Scheduled reports for NPM are duplicated.
• During database maintenance when SolarWinds Platform Services are shut down, gaps in monitoring may occur:
  • Gaps in monitoring on the primary SolarWinds Platform server during the backup period.
  • Gaps in monitoring on the secondary SolarWinds Platform server during the restore period.
  • There might be inconsistencies in some charts in the secondary environment because not all counters are measured at the exact same time in both environments.

Active-Active deployment requirements 

• SolarWinds Platform must be 2016.2 and later.
• Server hardware and software specifications must meet or exceed the requirements of your SolarWinds Platform environment. See SolarWinds Platform requirements in the Customer Success Center.
• SQL database requirements must meet or exceed the requirements for the SolarWinds Platform database. See SolarWinds Platform requirements.
• All user account credentials must have administrative rights on both the primary SolarWinds Platform server and the secondary SolarWinds Platform server in the SolarWinds Platform Active/Active configuration.
• Licenses must be registered for all SolarWinds Platform products installed on your secondary SolarWinds Platform server.

SolarWinds recommendations for the SQL database in an Active/Active deployment 

• Install the database for the secondary SolarWinds Platform server on its own physical server.
• Install the proprietary SQL server management tool on both the primary and the secondary database servers.
• Do not use a Microsoft SQL Server Express database. Its storage is limited to 10 GB, and RAM is limited to 1 GB.
• Prepare the credentials:
  • Have available the password to the sa accounts for both your primary and your secondary SolarWinds Platform database servers.
  • Have available the credentials to accounts with administrative rights on both the primary and secondary SolarWinds Platform database servers.
• SQL AlwaysOn is supported in SolarWinds Platform products running SQL Server 2012 or later. Although that feature is not influenced by an Active/Active deployment, there are other considerations to be aware of.

Active/Active license requirements 

• All products installed on the primary server match all of the products installed on the secondary server.
• The license agreement requires that the secondary SolarWinds Platform instance be used solely to monitor the same entities that are monitored on the primary instance.
• The license levels for each installed product must match on the primary and secondary instance.

Preflight check 

• Verify that system requirements are met, all required software is installed, and required roles and features are enabled.
• Gather the information required to complete the installation.

Prepare for the install 

Set up the Active/Active deployment 

Prepare a separate database 

1. Log in to the server hosting your secondary SQL database.
2. Review the following script, and provide the database name. In this example, the database is called OrionTablesBackupDB.

   CREATE DATABASE OrionTablesBackupDB --<<==== Choose a DB name for the temporary storage. This will be further used in the scripts
   GO

3. Open the Microsoft SQL Management Studio, and run the updated script to create the database.
4. Create the database tables:
   1. In the SQL Management Studio, right-click the secondary database, and select Tasks > Generate Scripts.

      
      
      

   2. Select tables with the prefix dbo.Licensing_*.

      
      
      

   3. Complete the wizard. By default, the wizard generates only the schema, you don't need to modify anything. The script is created.
   4. Open the script, and modify the database name to the name of the database you created.
   5. Launch the script (F5) to create the tables.
      The list of the tables defines the tables to be backed up, and copied back after you restore the database. The script is created.

      

   6. In SQL Server Management Studio, select the helping database OrionTablesBackupDB, and launch the following script against it. The script creates stored procedures that move the data between the source (primary) and backup databases.

      IF NOT EXISTS (SELECT * FROM sys.types WHERE name='TablesToBackupType')
      BEGIN
      CREATE TYPE TablesToBackupType AS TABLE
      (
      [tableToBackup] [varchar](120) NOT NULL
      )
      END
      
      
      IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[sp_GetDelimitedListOfColumnsForTableNoIdentity]'))
      BEGIN
      DROP PROCEDURE sp_GetDelimitedListOfColumnsForTableNoIdentity
      END
      GO
      CREATE PROCEDURE sp_GetDelimitedListOfColumnsForTableNoIdentity (@currentTableName nvarchar(120), @columnListCommaDelimited nvarchar(max) out)
      AS
      DECLARE @loopCounter INT=0;
      DECLARE @tableColumns table (columnName varchar(100))
      SET @columnListCommaDelimited = ''
      DECLARE @currentColumnName nvarchar(max)
      DECLARE columnIterator CURSOR LOCAL FAST_FORWARD FOR SELECT columnName FROM @tableColumns;
      OPEN columnIterator
      INSERT INTO @tableColumns(columnName) select c.name from sys.columns c inner join sysobjects so on c.object_id=so.id WHERE c.is_identity=0 AND so.name= @currentTableName
      DECLARE @columnCount int
      SET @columnCount = (SELECT Count(*) from @tableColumns)
      WHILE @loopCounter < @columnCount
      BEGIN
      FETCH NEXT FROM columnIterator Into @currentColumnName;
      IF @loopCounter < @columnCount-1
      SET @columnListCommaDelimited += (@currentColumnName + ', ')
      ELSE
      SET @columnListCommaDelimited += @currentColumnName
      SET @loopCounter = @loopCounter + 1;
      END
      CLOSE columnIterator;
      DEALLOCATE columnIterator;
      GO
      
      
      IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[sp_CopyFromSourceDBtoTargetDBnoIdentity]'))
      BEGIN
      DROP PROCEDURE sp_CopyFromSourceDBtoTargetDBnoIdentity
      END
      GO
      
      
      CREATE PROCEDURE sp_CopyFromSourceDBtoTargetDBnoIdentity (@sourceDB nvarchar(120), @targetDB nvarchar(120), @tablesToBackup TablesToBackupType READONLY)
      AS
      DECLARE @loopCounter INT=0;
      DECLARE @currentTableName varchar(100)
      DECLARE tablesIterator CURSOR LOCAL FAST_FORWARD FOR SELECT tableToBackup FROM @tablesToBackup;
      OPEN tablesIterator
      WHILE @loopCounter < (SELECT Count(*) from @tablesToBackup)
      BEGIN
      FETCH NEXT FROM tablesIterator Into @currentTableName;
      DECLARE @targetTableCleanupCommand nvarchar(max) = 'DELETE FROM ' + @targetDB + '.dbo.' + @currentTableName;
      EXEC sp_executesql @targetTableCleanupCommand
      IF EXISTS (select c.name from sys.columns c inner join sysobjects so on c.object_id=so.id WHERE c.is_identity=1 AND so.name= @currentTableName)
      BEGIN
      DECLARE @reseedTargetTableIdentityCommand nvarchar(max) = 'DBCC CHECKIDENT (''[' + @currentTableName + ']'', RESEED, 0)';
      EXEC sp_executesql @reseedTargetTableIdentityCommand -- Reset the identity value back to 0 to avoid identity type overflow by often rewrite operations
      END
      DECLARE @columnList nvarchar(max) = ''
      EXEC sp_GetDelimitedListOfColumnsForTableNoIdentity @currentTableName, @columnList out
      DECLARE @backupTableCommand nvarchar(max) = 'INSERT INTO ' + @targetDB + '.dbo.' + @currentTableName + '('+ @columnList + ') SELECT '+ @columnList +' FROM ' + @sourceDB + '.dbo.' + @currentTableName;
      EXEC sp_executesql @backupTableCommand
      
      
      SET @loopCounter = @loopCounter + 1;
      END
      CLOSE tablesIterator;
      DEALLOCATE tablesIterator;
      GO

      -- Scripts are not supported under any SolarWinds support program or service.
      -- Scripts are provided AS IS without warranty of any kind. SolarWinds further
      -- disclaims all warranties including, without limitation, any implied warranties
      -- of merchantability or of fitness for a particular purpose. The risk arising
      -- out of the use or performance of the scripts and documentation stays with you.
      -- In no event shall SolarWinds or anyone else involved in the creation,
      -- production, or delivery of the scripts be liable for any damages whatsoever
      -- (including, without limitation, damages for loss of business profits, business
      -- interruption, loss of business information, or other pecuniary loss) arising
      -- out of the use of or inability to use the scripts or documentation.

Synchronize the SolarWinds Platform Active/Active environment for maintenance 

When to synchronize databases? 

• During the scheduled database maintenance
• When SolarWinds Platform objects are added, removed, or modified in the SolarWinds Platform. For example:
  • Devices
  • Credentials
  • Custom properties
  • Application monitor templates
  • Application components

Maintenance step 1: Synchronize the databases 

1. Back up the source database (primary SQL server):
   Log in to the primary SQL server, and run the backup script.
   Consult the script with your database administrator to adjust preferred media and backup style.
   The following example backs up the database to a shared network drive.

   USE master;
   BACKUP DATABASE SolarWindsOrionMain
   TO DISK = '\\10.140.26.196\Backups\DBBackup.bak'
   GO

2. Restore to the target DB (secondary SQL server):
   Log in to the secondary SQL server, and run the restore script.
   The following example script:
   • backs up the licensing data to the helping database (temporary storage, called OrionTablesBackupDB in this example)
   • restores the primary database backup on the secondary SQL server database
   • copies the licensing data from the helping database to the secondary SQL server database
   Contact your database administrator for the correct restore script for your database. Adjust the information with comments to your environment.

   USE [OrionTablesBackupDB] -- <== Set here the name of the backup DB
   DECLARE @tablesToBackup TablesToBackupType
   INSERT INTO @tablesToBackup select name from sys.tables;
   
   DECLARE @backupDB nvarchar(max) = 'OrionTablesBackupDB' -- <== Set here the name of the backup DB (temporary storage)
   DECLARE @mainDB nvarchar(max) = 'SolarWindsOrionSecondary' -- <==Set here the name of the backup SolarWinds Platform DB
   
   DECLARE @dbBackupLocation nvarchar(max) = '\\10.140.26.196\Backups\DBBackup.bak' -- <== Use this if you use DISK storage. If you use other ways, like TAPE, check directly @restoreCommand to modify
   
   --Copy data to backup DB
   EXEC sp_CopyFromSourceDBtoTargetDBnoIdentity @mainDB, @backupDB, @tablesToBackup
   
   --Restore itself
   
   DECLARE @restoreCommand nvarchar(max) = '
   SET DEADLOCK_PRIORITY HIGH;ALTER DATABASE [' + @mainDB + '] SET SINGLE_USER WITH ROLLBACK IMMEDIATE; RESTORE DATABASE [' + @mainDB + '] FROM DISK=''' + @dbBackupLocation + ''''
   exec sp_executesql @restorecommand
   
   --Copy data back
   
   EXEC sp_CopyFromSourceDBtoTargetDBnoIdentity @backupDB, @mainDB, @tablesToBackup

Troubleshooting 

Database left in Single User Mode during the restore

Broken login after the restore

Maintenance step 2: Run the post-restore script 

Run the post-restore script:

USE SolarWindsOrionSecondary --<<======= UPDATE to the target DB name
DECLARE @hostnamesMap table(sourceHostname varchar(100), targetHostname varchar(100))
/*DEFINE servers mapping. First element is the name of the server from source database, second from target. Add row per each another server (APE, AWS) in the system*/
INSERT INTO @hostnamesMap(sourceHostname, targetHostname) VALUES
('source1', 'target1') --<<====== update
,('source2', 'target2') --<<====== update/remove/add next pair if needed


DECLARE enginesIterator CURSOR LOCAL FAST_FORWARD FOR SELECT sourceHostname, targetHostname FROM @hostnamesMap;
DECLARE @loopCounter int=0;
DECLARE @serversCount int = (SELECT Count(*) from @hostnamesMap)
DECLARE @currentTargetHostname varchar(100)
DECLARE @currentSourceHostname varchar(100)
OPEN enginesIterator
WHILE @loopCounter < @serversCount
BEGIN
FETCH NEXT FROM enginesIterator Into @currentSourceHostname, @currentTargetHostname;
/*UPDATE SECTION BEGIN*/
UPDATE ENGINES SET ServerName = @currentTargetHostname WHERE ServerName = @currentSourceHostname
UPDATE Websites SET ServerName = @currentTargetHostname WHERE ServerName = @currentSourceHostname
UPDATE WebSettings SET SettingValue = @currentTargetHostname WHERE SettingName='JobSchedulerHost' AND SettingValue = @currentSourceHostname;
UPDATE WebSettings SET SettingValue = @currentTargetHostname WHERE SettingName='LicensingMainServerName' AND SettingValue = @currentSourceHostname;
UPDATE OrionServers SET HostName = @currentTargetHostname WHERE HostName = @currentSourceHostname
UPDATE Sites SET Name=@currentTargetHostname, Host=@currentTargetHostname WHERE Host=@currentSourceHostname
/*UPDATE SECTION END*/
/*CLEANUP SECTION BEGIN*/
DELETE FROM PendingNotifications WHERE Subscription_Id IN (SELECT Id FROM Subscriptions WHERE EndpointAddress LIKE 'net.tcp://' + @currentSourceHostname + '%' OR EndpointAddress LIKE 'inproc://' + @currentSourceHostname + '%' OR EndpointAddress LIKE 'active://' + @currentSourceHostname + '%' OR EndpointAddress LIKE 'bus://' + @currentSourceHostname + '%');
DELETE FROM Subscriptions WHERE EndpointAddress LIKE 'net.tcp://' + @currentSourceHostname + '%' OR EndpointAddress LIKE 'inproc://' + @currentSourceHostname + '%' OR EndpointAddress LIKE 'active://' + @currentSourceHostname + '%' OR EndpointAddress LIKE 'bus://' + @currentSourceHostname + '%';
DELETE FROM ServiceDirectoryEntries
/*CLEANUP SECTION END*/


SET @loopCounter = @loopCounter + 1;
END
CLOSE enginesIterator;
DEALLOCATE enginesIterator;
GO   

Handle passive monitoring (NetFlow, Syslog, and SNMP Traps) for Active/Active deployments 

Configure NetFlow monitoring 

• ip flow-export version 5
• ip flow-export destination <ip_address_primary> 2055
• ip flow-export destination <ip_address_secondary> 2055

Configure Syslogs 

• NodeName(config)#logging ip_address_primary
• NodeName(config)#logging ip_address_secondary

Configure SNMP traps 

• NodeName(config)#snmp-server host ip_address_primary public
• NodeName(config)#snmp-server host ip_address_secondary public