Planning the layout of a redundant system, Planning the layout of a redundant system – 9 – Rockwell Automation FactoryTalk View Site Edition Users Guide User Manual
Page 353
![background image](/manuals/581457/353/background.png)
14
•
S
ETTING
UP
F
ACTORY
T
ALK
SYSTEM
AVAILABILITY
14–9
•
•
•
• •
14
•
Pla
ceho
lde
r
Host computer hardware failures,
provide backup computers to host application
software such as FactoryTalk View SE.
FactoryTalk software failures,
set up redundant FactoryTalk View SE and
RSLinx Enterprise application servers.
Planning the layout of a redundant system
The servers you can use in a FactoryTalk View SE network distributed application are
separate entities, which means they can be hosted on any computer on the network.
However, when designing a redundant control system, you should keep in mind the
system requirements that apply to different types of servers.
For example, to support FactoryTalk Network Directory availability, it is recommended
that you run the directory server on a computer that you plan to keep running.
This could be the same computer used to host a FactoryTalk View SE Server, or a
Rockwell Automation Device Server (RSLinx Enterprise).
Example: An application with two redundant HMI server pairs
In its simplest form, a redundant FactoryTalk View SE application might consist of one
pair of redundant FactoryTalk View SE Servers (also called HMI servers), and one pair of
redundant RSLinx Enterprise servers.
In this example, two redundant server computer pairs host primary and secondary HMI
servers, and RSLinx Enterprise data servers.
Do not run the FactoryTalk Network Directory on the same computer as a Windows domain
controller.
The FactoryTalk Network Directory (on the first primary computer in the following illustration)
cannot be made redundant. For information about what happens when the Network Directory
fails, see page 14-8.