Configure the material-enabled FactoryTalk Batch Server for manual failover

On the Material server computer, start the Network Editor.

Select the network model for the primary

FactoryTalk Batch

Server.

Right-click BATCHSERVER in the tree and select Remove Server.

From the File menu, select

Synchronize

.

Select the network model for the Material server.

Right-click any <Undefined>

FactoryTalk Batch

Server in the tree, and then click Add Server.

Type a name in the Alias box.

Select the Computer Name box, and then select the computer to use as the secondary server.

From the File menu, select

Synchronize

.

Start the process-connected device communication software on the secondary server. The secondary server computer needs to communicate with the process controller running the phase logic.

Ensure that the project directories for the secondary server are assigned to local directories. Use the Server Options dialog box in

FactoryTalk Batch Equipment Editor

.

Use the

FactoryTalk Batch

Service Manager to start the

FactoryTalk Batch

Server software 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.

If you are also using

e

Procedure

, use the

FactoryTalk Batch

Service Manager to start the

e

Procedure

Server on the secondary server computer.

For each computer running the

FactoryTalk Batch View

, enter the computer name of the secondary server as the NET registry key value.

Stop and restart each

FactoryTalk Batch View

instance and any other software that communicates directly with the

FactoryTalk Batch

Server. This causes the

FactoryTalk Batch View

instance to connect with the secondary server.