Redundant servers
To help ensure that critical data remains available to clients in a distributed automation system, even during server disruptions, the
FactoryTalk
platform enables several built-in features that support system availability.Configuring a local cache file enables a client computer to continue to run when disconnected from the network directory server, using a local cache of directory information. While disconnected, the client cannot change directory information, such as areas, servers, and user accounts. However, a cache does not provide continuity of service in the event of server failure.
To decrease the risk of service interruption due to server failure,
FactoryTalk
applications can include two types of servers that can be made redundant through standard configuration options:- FactoryTalk View SEServers (HMI servers)
- Data servers (FactoryTalk Linxserver, OPC DA server,FactoryTalkResource and Status server,FactoryTalkBatch server, Tag Alarm and Event server, OPC UA server,RSLinx Classicand otherOPC2.0 Data Access servers)
Each of these types of servers can be hosted one the same or on different computers on the
network. Once configured, each redundant pair of servers is available to all clients
participating in the same network application. Adding additional client computers does not
require any additional configuration.
Data servers, such as
OPC
data servers and device-based servers (FactoryTalk Linx
), allow clients to access information in programmable controllers, in other hardware devices, and from other data servers that comply with the OPC
-DA (OLE for Process Control – Data Access) 2.0 specification.Use
FactoryTalk Administration Console
or FactoryTalk View Studio
to set up redundancy
options for data servers.
TIP:
To set up redundancy options for HMI servers, use
FactoryTalk View Studio
.OPC
UA Server redundancy is configured independently of the FactoryTalk
platform.Provide Feedback