Define secondary servers (optional)

Configure
FactoryTalk® Batch
 to store batch journals and batch restart information in two separate locations. If there is a hardware failure on the primary
FactoryTalk Batch
 Server computer, using a secondary server allows for a manual failover.
The second computer must be capable of running the server. Secondary servers are defined by specifying the primary and secondary restart paths. If the system experiences a failure, these paths indicate where system files are written. If a secondary path is not specified,
FactoryTalk Batch
 does not write any secondary files.
TIP:
Archiver recovery
—The
eventdir.txt
 and the
archque.txt
 are not updated as secondary files. As part of the manual failover procedure, manually copy the files from the primary directory to the secondary directory.
FactoryTalk Batch
 can be configured to store batch journals and batch restart information in two separate locations.
To define secondary servers
  1. Open
    FactoryTalk Administration Console
     and sign in to the
    FactoryTalk
     Network Directory.
  2. In
    FactoryTalk Administration Console
    Explorer
    , right-click the primary
    FactoryTalk Batch
     Server and select
    Properties.
    .
    TIP: This procedure requires administrator privileges.
  3. In the
    FactoryTalk Batch
     Services Properties dialog, select the
    Secondary Server
     tab.
  4. Select
    Enable secondary FactoryTalk Batch Server
    .
  5. Select the
    Computer hosting the secondary FactoryTalk Batch Server
     browse button and browse to the machine where the secondary server is installed. Or you may type in the name of the computer if known.
  6. In the
    Batch creation
     area:
    1. Select a
      Create ID range
       value. For the purpose of batch identification, the secondary
      FactoryTalk Batch
       Server generates a unique
      CreateID
       for each batch at batch creation. The
      Create ID range
       field controls the range of IDs that the secondary
      FactoryTalk Batch
       Server can use when generating a
      CreateID
      . This value must be unique from the value configured for the primary
      FactoryTalk Batch
       Server in the
      General
       tab.
    2. (Optional) Update the
      Default Batch ID
       value. This is the value the operator will see in the
      FactoryTalk Batch View
      Batch Creation
       page in the
      Batch ID
       property.
  7. Select
    Apply
    .
  8. In the
    FactoryTalk Batch Services Properties
     dialog, select the
    Project Settings
     tab.
  9. In the
    Server
     box, select
    Primary
    .
  10. In the
    Server directories
    Project path strategy
    , select
    Default paths
    .
  11. In the
    Server directories
    Project directories
     area, select the
    Duplicate Journal
     browse button. The
    Select Directory
     dialog opens.
  12. Select the location of the secondary server journal files in the
    FTBATCH_PROJECTS
     share on the primary server's hard drive, and select
    OK
    . The default is
    C:\Users\Public\Public Documents\Rockwell Automation\Batch
    .
    TIP:
    The recommended practice is to mirror the
    Event Journal
     and
    Duplicate Journal
     directories. For example:
    • The primary
      FactoryTalk Batch
       Server's
      Event Journal
       directory is the secondary
      FactoryTalk Batch
       Server's
      Duplicate Journal
       directory.
    • The primary
      FactoryTalk Batch
       Server's
      Duplicate Journal
       directory is the secondary
      FactoryTalk Batch
       Server's
      Event Journal
       directory.
  13. In the
    Server directories
    Project directories
     area, select the
    Duplicate Restart
     browse button.
    The
    Select Directory
     dialog opens.
  14. Select the location of the secondary server restart files in the
    FTBATCH_PROJECTS
     share on the primary server's hard drive (the default is
    C:\Users\Public\Public Documents\Rockwell Automation\Batch
    ), and then click
    OK
    .
    TIP: The recommended practice is to mirror the
    Restart
     and
    Duplicate Restart
     directories. For example:
    • The primary
      FactoryTalk Batch
       Server's
      Restart
       directory is the secondary
      FactoryTalk Batch
       Server's
      Duplicate Restart
       directory.
    • The primary
      FactoryTalk Batch
       Server's
      Duplicate Restart
       directory is the secondary
      FactoryTalk Batch
       Server's
      Restart
       directory.
  15. Locate and select the
    MyProject\restart
     folder located in the
    FTBATCH_PROJECT
     share on the secondary server’s hard drive, and select
    OK
    .
  16. In the
    Server
     box, select
    Secondary
    .
  17. In the
    Server directories
    Project path strategy
    , select
    Default paths
    .
  18. Repeat 11 to 14 for the secondary server computer. The
    Duplicate Journal
     and
    Duplicate Restart
     path can remain blank or point to another secondary server. Additionally, you must configure a data server to communicate with the process controller on the secondary server computer. The secondary server computer needs to communicate with the process controller that is running the phase logic.
    TIP: You must also verify that the primary and secondary journal project directories are defined.
  19. Select
    Apply
     to save the data in the
    Project Settings
     tab.
  20. Select
    OK
     to save the data in each tab of the
    FactoryTalk Batch Services Properties
     dialog and close the dialog.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal