Javascript must be enabled to download our products and perform other essential functions on the website.

ionicons-v5-m
ionicons-v5-j
Buy Now Download Free Trial
ionicons-v5-m
ionicons-v5-f

This help page is for version 9.2. The latest available help is for version 9.3.

Automatic Fail Over

The Automatic Fail Over feature lets you create a second monitoring server which will automatically mirror your primary Central Monitoring Service. This Fail Over Slave server will sit quietly and listen for heart beats from the primary monitoring service. If a heart beat isn't received for 5 minutes, it will take over monitoring, alerting and reporting.

Data that is automatically mirrored to the Fail Over Slave are:

  • configuration database (groups, computers, servers, monitors, actions, reports)
  • Satellite registration database
  • application registry settings
  • System Alert definitions
  • UserList.txt and LDAP/Active Directory settings for remote access
  • license file(s)
  • shared report files (report templates, graphics, maps, etc)
  • MIB files
  • language translation files
  • oemconfig.ini (optional file)

Because all configuration is 'owned' by the Central Monitoring Service, you can connect to the Fail Over Slave with the Console, but won't be able to change much.

Setup

To use the Automatic Fail Over feature, install a second Central Monitoring Service on a second server, just like you installed the original. Don't worry about adding licenses or importing configuration, etc.

Prerequisites

  1. The PA File Sight service on both servers need to be using the same MS SQL Server. This can be changed in Database Settings.
  2. PA File Sight on both servers should use the same service account.
  3. Use the same version of PA File Sight on both servers. You can get the installer from the Central Server at C:\Program Files\PA File Sight\Install\Setup.exe.

On the Fail Over Slave

This second installation will be referred to as the Fail Over Slave. On the Fail Over Slave:

  1. Start the Console on the Fail Over Slave and connect. Go to Settings and check or change the port if needed.
  2. Set HKEY_LOCAL_MACHINE\software\PAFileSight   [DWORD]FO_IsSlave = 1
  3. Restart the PA File Sight service
  4. Open a browser and point it to https://127.0.0.1:{port}/ to ensure the Windows Firewall is not blocking access

On the Central Server (Master)

Next, get on the main Central Monitoring Service (the Master in the Master-Slave configuration). Start the Console and go to Advanced Services > Failover Status > Configure Fail Over.

You will see the dialog below. Enter the Slave's host name and port.

Press the Check Settings button. This will test the settings on both the Master and Slave. If any items are not green check boxes, select that item to get additional information.

Once all items are green, press OK and the Master and Slave will begin synchronizing configuration information.

Using Satellites?

If you are using the Satellite Monitoring Service on other servers, you need to give those other servers the hostname or IP address of the Fail Over Server so the Satellites can switch to the Fail Over Server in the event that the Central Monitoring Service goes down. This can be done in two ways:

  • Visit every Satellite - you can manually add an additional host:port to each Satellite's configuration application via the Advanced button.
  • Bulk Config - you can send the Fail Over Server's host:port to all the Satellites using the Bulk Config operation Satellites: Set Central Server Hosts. The main host:port is probably already configured on the Satellites, so you'll most likely be setting the Backup 1 host:port entry to point to the Fail Over Slave. Note that Satellite will test the host:port given, and if it can't connect, it will not set the value.

Check Status

The Fail Over Status report will show the Automatic Fail Over system's health and readiness, as well as recent communications between the Master and Slave.

You can click the (Slave's status report) link to see the Slave's view of the fail over system's health.

Failing Over

When the Fail Over Slave hasn't heard from the Central Server for 5 minutes, it will take over monitoring. If there are Satellites, they will automatically switch to the Fail Over Slave within a few minutes after that.

When the Central Server comes back up, the Fail Over Slave will automatically stop monitoring, and any Satellites that were connected to it will automatically switch back to the Central Server after a minute or two.

PA File Sight

Help Map