Peer-to-peer failover functionality

The probe supports failover configurations where two probes run simultaneously. One probe acts as a master probe and sends alerts to the ObjectServer. The other probe acts as a slave probe and remains on standby. If the master probe fails, the slave probe is activated.

Note: Microsoft SCOM 2016 does not allow the same event to be automatically forwarded to more than one connector at a time. This means that the peer-to-peer failover behavior of the Probe for Microsoft SCOM 2016 is slightly different from the standard peer-to-peer failover behavior of most probes.

You can use a failover configuration by starting two instances of the probe, one master and one slave. Both probes must use the same connector name, as specified by the ConnectorName properties in their respective properties files. Both probes must also use the same peer port, as specified by their respective PeerPort properties.

If you set values for the ConnectorUser and ConnectorPassword properties on the master instance of the probe, you must also set these properties to the same values on the slave instance of the probe.

Note: If you have assigned the Operations Manager Administrator user role to the probe's user group in the Microsoft SCOM 2016 probe, you do not have to specify a value for the ConnectorUser and ConnectorPassword properties.

Unlike standard peer-to-peer failover behavior for most probes, the slave instance of the probe does not connect to Microsoft SCOM 2016 at the same time as the master instance. Instead, the slave probe connects to Microsoft SCOM 2016 and starts to process events only after it detects the loss of a heartbeat signal from the master probe. When the master probe is running again, the slave probe stops polling Microsoft SCOM 2016 for new events.