Enabling failover on the Intrusion Manager role - Receiver 3.2.0

Receiver Intrusion Detection Extension Guide 3.2.0
Applies to
Receiver 3.2.0
Last updated
2024-03-28
Content type
Guides > Plugin and extension guides
Language
English
Product
Receiver
Version
3.2

To improve the availability of your Intrusion Manager role, you can add a secondary server on standby. If the primary server hosting the role becomes unavailable, the role is automatically transferred to the secondary server.

Before you begin

What you should know

  • For more information, see Role failover on the TechDoc Hub.
    IMPORTANT: Security Center does not handle the failover of role databases. For roles that connect to a database, the database server must be hosted on a third computer, separate from the servers hosting the role. All role servers must have read and write access to the database server. To protect your data, perform regular backups of the role database.
  • If the plugin is configured to use HTTPS, the Events certificate needs to be valid for the main and failover server. The option to Create a self-signed certificate will not work as that certificate would be only valid for the server where the plugin is currently running.

Procedure

  1. From the Config Tool homepage, open the Plugins task.
  2. From the entity browser, select the Receiver plugin role and click the Resources tab.
  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.
    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)". If it does, rename the database server to match the remote server you prepared in advance for your Intrusion Manager role.
    1. Back up your Intrusion Manager role database and restore it on a server that is not hosting your Intrusion Manager role.
    2. Enable remote access to the Intrusion Manager role database that you restored.
    3. Change the Database server to the server hosting your Intrusion Manager role database.
      For example, REMOTESERVER\SQLEXPRESS.
  8. Click Apply.
Browse