General Guidelines for Using the Server-to-Server Collector

It is recommended you follow these general guidelines when using the Server-to-Server Collector:

• Use polled triggers to perform scheduled data transformations like daily or hourly averages. Use unsolicited triggers to replicate data in real time, as it changes.
• Use event-based triggers to replicate data throughout the day. The samples can be held in an out- going store and forward buffer when necessary. You cannot schedule batch replication of raw samples. For example, you cannot, at the end of the day, send all raw samples for tags to the destination.
• Use event-based triggers to replicate data throughout the day. The samples can be held in an out- going store and forward buffer when necessary. You cannot schedule batch replication of raw samples. For example, you cannot, at the end of the day, send all raw samples for tags to the destination.
• All input source tags for the calculations must originate from the source archiver. For instance, you cannot directly add a tag from server1 plus a tag from server2 and place the result on server2. You could, however, collect tags from server1 to server2 and then use the Calculation Collector or Server-to-Server Collector to accomplish this. This requires two Server-to-Server Collectors, one running on each machine. You could also use the Historian OLE DB Provider.