Redundant system checklist
- Last UpdatedAug 14, 2025
- 2 minute read
Refer to the following checklist when planning your redundant system:
Determine the Redundant System Configuration
Evaluate what type of redundant configuration is a better fit for your system. Both the Dedicated Standby and Load Shared configurations provide a reliable and robust solution, but depending on the process requirements and system architecture, one of the configurations may be more efficient than the other.
Analyze the Expected System Behavior After Failover
It is very important to understand how scripts are executed after a failover. Scripting considerations explains how scripts behave in a failover condition.
Identify which attributes need to be retentive after a failover. See Checkpoint attributes for additional information.
Distribute Data Traffic
To make the best use of network bandwidth, distribute the traffic coming in and out of the ApplicationObject Servers over different networks. For example, the need for data from the control network may be more critical than the data requirements of the supervisory system. Distributing data traffic through separate networks requires the use of multiple network cards in a server.
Note: Although distributing data traffic through separate networks is not required, multiple NICs are used for optimal communication in the network figures that appear in this chapter.
Rename Each Local Area Connection When Using Multiple Network Adapters
The operating system detects network adapters and automatically creates a local area connection in the Network Connections folder for each network adapter.
Renaming each local area connection to reflect its network eliminates confusion. Add or enable the network clients, services, and protocols required for each connection. When doing so, the client, service, or protocol is added or enabled in all other network and dial-up connections.