How does the Archive Manager work in a Fault-Tolerant environment?
Release : 21.2
Component : Archive Manager
You can run the Archive Manager on the secondary SpectroSERVER host in a fault-tolerant SpectroSERVER environment. This secondary Archive Manager only provides visibility to events in OneClick when the primary Archive Manager is down.
Primary or secondary SpectroSERVER locally stores events in the following two scenarios:
When you start the secondary Archive Manager, it acts as a client to the primary SpectroSERVER to receive and log events as they are created. This behavior does not affect the normal connection between the primary SpectroSERVER and the primary Archive Manager. As soon as the primary Archive Manager goes down, OneClick fails over to the secondary Archive Manager to provide event data.
When the primary SpectroSERVER host itself goes down, the secondary SpectroSERVER locally stores events but also forwards events to the secondary Archive Manager. When the primary Archive Manager comes up, the secondary SpectroSERVER transfer all the locally stored events to it.
The primary SpectroSERVER stops. The secondary SpectroSERVER then forwards events and statistical information to the primary Archive Manager that is running on the server that hosts the primary SpectroSERVER. When the primary SpectroSERVER restarts, no event and statistical data have been lost.
The computer where the primary SpectroSERVER and the primary Archive Manager are running stops operating completely. The secondary SpectroSERVER then caches event and statistical data in its database until the primary SpectroSERVER computer comes back online. If a secondary Archive Manager is running, historical, and real-time information is available in OneClick, but the information is still cached for transfer to the primary Archive Manager.
Restart both the primary Archive Manager and the primary SpectroSERVER if their server does down, or if the primary SpectroSERVER stops operating.
Note: It is no longer necessary to start the Archive Manager before the SpectroSERVER, the cached events from the secondary SpectroSERVER can be transferred at any time, even after the primary SpectroSERVER has started logging new events.
Follow these steps:
Please review the following KB article about sizing the temporary local Event Storage on the SSdb database: