Configure the FactoryTalk Batch Server for manual failover

FactoryTalk Batch
 can be configured to store batch journals and batch restart information in two separate locations. The use of a secondary server allows you to perform a manual failover if there is a hardware failure on the primary
FactoryTalk Batch
 Server. The second computer must be capable of running the server.
You must install your area model file and all recipe files (and all instruction files if using
e
Procedure
) on both the primary server and the secondary server.
TIP:
Archiver recovery
 - As part of the manual failover procedure you must manually copy the
eventdir.txt
 and the
archque.txt
 from the primary directory to the secondary directory.
When the
FactoryTalk® Batch
 Server fails, complete these steps.
To configure the
FactoryTalk Batch
 Server for manual failover:
  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. Make sure that the secondary server’s project directories are assigned to local directories in
    FactoryTalk® Administration Console
    .
    TIP: To configure project directories, right-click an application or area name in
    FactoryTalk Administration Console
    Explorer
     and select
    Properties
    . In the
    FactoryTalk Batch Services Properties
     dialog, select the
    Project Settings
     tab.
  3. Use the
    FactoryTalk Batch Service Manager
     to start the
    FactoryTalk Batch
     Server on the secondary server computer, and select
    Warm
    ,
    Warm All
    , or
    Hot
     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, and clear the
    Cold Restart
     checkbox.
  5. Start the
    FactoryTalk® Batch View™
     Server on the secondary server.
  6. Redirect any
    FactoryTalk Batch View
     clients to the secondary URL.
    TIP:
    For a Warm Restart or Warm All Restart, 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.
    A Hot Restart attempts to restore a batch into its last known state, including the states of transitions and the modes of recipe procedures.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal