Configure the FactoryTalk Batch Server for manual failover

When the
FactoryTalk Batch
Server fails, complete these steps.
TIP:
If you are using
FactoryTalk Batch
Material Manager
, refer to the procedure for material-enabled configuration.
To configure the FactoryTalk Batch Server for manual failove
r:
  1. Start the process-connected device communication software on the secondary server. The secondary server computer needs to communicate with the process controller that is running the phase logic.
  2. Ensure that the secondary server’s project directories are assigned to local directories in the
    Server Options
    dialog box located in
    FactoryTalk Batch Equipment Editor
    .
  3. Use the
    FactoryTalk Batch
    Service Manager to start the
    FactoryTalk Batch
    Server on the secondary server computer, select
    Warm
    or
    Warm All
    as the startup type. The secondary server allows the batches to be restarted based upon information written by the primary server.
  4. (optional) If you are also using
    e
    Procedure
    , use the
    FactoryTalk Batch
    Service Manager to start the
    e
    Procedure
    Server on the secondary server computer.
  5. For each computer running
    FactoryTalk Batch View
    , enter the secondary server’s computer name as the NET registry key value.
  6. Stop and restart each
    FactoryTalk Batch View
    instance and any other software that communicates directly with the
    FactoryTalk Batch
    Server. This causes the instance to connect with the secondary server.
    TIP:
    The existing batches are placed in the MANUAL mode with transitions in the HELD state. Place the batches in AUTOMATIC mode, clear the failures, and then restart the batch.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal