Configure Scheduler Redundancy

Scheduler operates as a core component of the Plant SCADA reports server. This means you can use report server redundancy to help maintain the operation of schedules during periods of system instability.

Redundancy support for Scheduler is provided as follows:

• When a connection is established, Scheduler's files are synchronized (merged) between the peer report servers.

• Only the active server will execute the schedules. If both servers are running, the active server will be the one that started first.

• If a network outage occurs, the primary will become active after communication is restored.

• When both servers are online, changes to the Scheduler file are replicated across both servers.

• If one of the report servers becomes inoperative, the schedules will run on the remaining reports server. When the inoperative report server returns online, the client will remain with the current reports server.

For more information, see Reports Server Redundancy.

Note: At startup, Scheduler may begin executing actions before other server processes in the system are available. This may result in the action not completing successfully. If this occurs, use the Citect.ini parameter [Scheduling]StartDelay to delay the startup of the Scheduler engine. This allows time for the other server processes of the system to come online before any scheduled actions are initiated.