Rockwell Automation FactoryTalk View Site Edition Users Guide - Manual (Page 374)

F ACTORY T ALK V IEW S ITE E DITION U SER ’ S G UIDE
14–30
• •
•
•
•
About alarm monitoring on the secondary server
While the primary HMI server is active, the secondary server runs its alarm monitoring
system in backup mode. This means that alarm states are synchronized even if you have
not set up the secondary server to start alarm monitoring on demand.
The backup mode that runs on the secondary server only keeps alarm states synchronized;
it does not detect alarms.
When the system fails over to the secondary server, alarm monitoring starts on that server
automatically, as if it was running on the primary server.
When the system switches back to the primary server, alarm monitoring starts on that
server automatically, while the secondary server returns to standby mode.
Centralize storage of diagnostic and alarm log data
Diagnostic log files are stored on every computer where system activity is generated.
For network distributed applications, it is highly recommended that you log diagnostic
and HMI tag alarm information to a central ODBC database, such as Microsoft SQL
Server, even for HMI servers that are not redundant.
A central, system-wide ODBC log can be made secure and redundant through features of
the database. Central logs also simplify troubleshooting, by letting you search all
diagnostic information in one location.
For additional protection, it is also recommended that you set up FactoryTalk View SE
local diagnostic and alarm logs to buffer logged data, in the event that communications
with the ODBC database are lost.
For information about setting up a central ODBC database:
 For diagnostic logs, see Chapter 15, Logging system activity.
 For HMI tag alarm logs, see Chapter 11, Setting up HMI tag alarms.
Determine which server will run events
Events that are triggered by an event detector, are not synchronized specifically between
primary and secondary HMI servers.
However, it is possible to manage which server is responsible for detecting and running
events, so that only one server is active at a time.
If FactoryTalk View SE is monitoring a large number of HMI tags for alarms, it is possible that
alarms might be missed for tags that go into and out of alarm quickly. This might happen while
the system is failing over to the secondary or switching back to the primary server.