Moving data between historians
Hello community!
I'm exploring the Redundant Logging architecture, where a data collector+sender pair will move data to a primary and redundant historian servers. In the event one of the servers go down, I would manually copy all the data from the running historian and import it into the one where the communication has been severed. The isolated historian servers are not supposed to communicate with one another, which is why I need to manually execute the sync.
Is this possible? If so, could someone point me to the documentation covering this topic, please?
Thanks in advance!
-
Hi Bela ,
If dual-logging to two or more historians, the Sender would handle the data buffering in the event that a server goes down. That data is cached to disk until the Sender can reconnect to the Receiver/Historian, wherein the data is flushed out and logging continues as normal. There is no need to sync the data between the two as the other will catch up as soon as it comes back online and the buffered data is processed.
Hope that makes sense!
-
Hi Steve Mason ,
It makes sense, thanks for the explanation. Just to confirm, the sender+data collector pair would need to be installed on the same machine where the datasource is located for buffering to work, correct?
-
Bela
Not necessarily, but we prefer to be installed as close as possible to the source to avoid data loss. Sometimes the collector+sender is installed remotely from the source. In the event there is a break in communication between the collector and source, there is a potential for data loss. If we're installed locally to the source, that eliminates that potential communication issue. We like to be installed locally because our Sender can handle the buffering of data in case we lose connection to the historian.
-
-
Thanks Steve Mason, I appreciate your answer.
Have a great weekend!
Print this page