Enabling failover on the plugin role - Restricted Security Area Surveillance 1.1

Restricted Security Area Surveillance Plugin Guide 1.1

series
Restricted Security Area Surveillance 1.1
revised_modified
2017-09-01

To improve the availability of your 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

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 when the primary server becomes unavailable, either through failure or through scheduled downtime. Role failover is managed by the Directory role. Directory failover is managed by the Directory Manager role. For more information, see Role failover and Directory failover and load balancing.
IMPORTANT: Security Center does not handle the failover of role databases. To protect your data, perform regular backups of the role database. To ensure the high availability of your role database, consider using Database Mirroring or SQL AlwaysOn from Microsoft as your database failover solution.

Procedure

  1. From the Config Tool home page, open the Plugins task.
  2. Select your plugin role from the entity tree and click Resources.
  3. At the bottom of 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 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 currently hosting the role.

    IMPORTANT: The order in which the servers appear in the list corresponds to the order 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. After a failover occurs, if you want the primary server to take control of the role after it is restored, select the Force execution on highest priority server option.
    NOTE: By default, the role remains on the secondary server after a failover occurs to minimize system disruptions.
  7. Make sure that the role is not connected to a database on the local machine.
    You can tell that the database server is local to your machine if the name of the Database server starts with "(local)". If it does, change it to the remote database server you prepared in advance for your plugin role.
  8. Click Apply.