Enabling failover on the plugin role - Security Center Traffic Sensor Management 2.3

Security Center Traffic Sensor Management Plugin Guide 2.3

Applies to
Security Center Traffic Sensor Management 2.3
Last updated
Content type
Guides > Plugin and extension guides
English (United States)
Product line
City applications > Security Center Traffic Sensor Management

To improve the availability of the plugin role, you can add a secondary server on standby. If the primary server hosting the role becomes unavailable, the secondary server is automatically used.

Before you begin

  • Ensure that you have an expansion server available in your system to use as a failover server for your plugin role.
  • If your TSS plugin role is hosted on the main server, you must first move it to an expansion server.
    NOTE: If you must host the plugin role on the main server, you must also configure the Directory failover. Role failover is managed by the Directory role, and Directory failover is managed by the Directory Manager role. For more information, see Directory failover and load balancing.
  • Ensure that the TSS plugin role and the TSS plugin role database are not hosted on the same server. All servers hosting the TSS plugin role must have written access to the remote database server. For more information, see Connecting roles to remote database servers.

What you should know

Failover is a backup operational mode in which a role (system function) is automatically transferred from its primary server to a secondary server that is on standby. This transfer between servers occurs only if the primary server becomes unavailable, either through failure or through scheduled downtime. For more information, see Role failover in the Security Center Administrator Guide.
IMPORTANT: Security Center does not handle the failover of role databases. To protect your data, perform regular backups of the role database.


  1. From the Config Tool home page, open the Plugins task.
  2. Select your plugin role from the entity tree and click Resources.
  3. Under the Servers list, click Add an item ().
    A dialog box opens, listing all remaining servers on your system that are not yet assigned to this role.
  4. Select the server that you want to add as a secondary server and click Add.
    The secondary server is added below the primary server. The green LED indicates which server is hosting the role.
    NOTE: The servers are listed in the order that they are picked if a failover occurs. When the primary server fails, the role automatically switches to the next server on the list.
  5. To change the priority of a server, select it from the list, and click the or buttons to move it up or down the list.
  6. If you want the primary server to retake control after it is restored from a failover, select the Force execution on highest priority server option.
    NOTE: To minimize system disruption, the role remains on the secondary server after a failover occurs, by default
  7. Ensure that the role is not connected to a database on the local machine. You can determine that the database server is local to your machine if the name of the Database server starts with (local).
    1. If the database server is local to your machine, rename the database server to match the remote server you prepared in advance for your plugin role.
    2. Back up your plugin role database and restore it on a server that is not hosting the plugin role.
    3. Enable remote access to the plugin role database that you restored.
    4. Change the database server to the server hosting your <Plugin Name> plugin role database. For example:REMOTESERVER\SQLEXPRESS.