Failover Conditions

The following conditions trigger failovers in a redundant server configuration:

• Critical Services shutdown – If any of the following AVEVA Batch Management services fail (crash or do not run):

  AVEVA Batch Management

  • BatchManagement_IBMX (InBatch MX Interface)

  • BatchManagement_BatchMngr (Batch Manager)

  • BatchManagement_IBCli (InBatch Client Manager)

  • BatchManagement_LogMgr (AVEVA Batch Management Log Manager)

  • BatchManagement_RedMngr (AVEVA Batch Management Redundancy Manager)

  • BatchManagement_HistQMngr (AVEVA Batch Management History Manager); in turn shuts down BatchManagement_BatchMngr

    Note: If you have an active Batch which is running and the History Manager is down, then the Batch Manager shuts down and triggers a failover.

    AVEVA Batch Management with Foxboro DCS Extensions

  • BatchManagement_RptManager (AVEVA Batch Management Report Manager)

  • BatchManagement_IADriver (AVEVA Batch Management Foxboro DCS Interface)

  • BatchManagement_EventMngr (AVEVA Batch Management Foxboro DCS Event Manager)

• Exit and Shutdown of the Master server causes a graceful failover between the batch servers.

  Note: For the Critical Services shutdown and the Exit and Shutdown of the Master server, you must configure the InTouch BatchGuiControl ActiveX control of the client to fail over.

• Complete Communication Failure (Network Failure) – The AVEVA Batch Management Servers fail over but the InTouch client cannot fail over. Operator intervention is necessary on both the server side and client side. The operator must restart the InTouch View client.

• Power Failure (Master) – The AVEVA Batch Management Servers fail over. In this scenario, the InTouch client (using the BatchGuiControl) does not fail over. An operator must restart the InTouch View client. The BatchGuiControl does not detect the change in servers and still thinks that it has a connection to the master server.