JavaScript is off. Many parts of this site require JavaScript to function properly.

How to Sync Primary and Redundant Historians

Oct 5, 2018 8:17:32 AM / by Jeff Knepper

The fifteenth edition of a Q&A column with Gary Stern, President and Founder of Canary Labs. Have a question you would like me to answer? Email askgary@canarylabs.com
 askgarycolumnE15a
 

Dear Backed Up,

For redundancy, we push data from the Canary Collecter and Sender Service  to each of the Historian’s Receiver Services.  This means that both the primary and secondary Historian are getting the same constant data feed from any Canary Collector.   The Collecter’s Sender Service knows whether the Historian receives the data, and if not, the Sender’s Service will cache the data to local disk.  When the Historian and it’s Receiver Service are back online, all data is moved from the Sender Service cache to the Historian. 

Because of how we handle this, we do not need to have either Historian aware of one another and there is no need for either Historian to try to replicate the other.  Replication would be potentially dangerous, especially if one of the Historians would have a corrupt file or if someone accidently deleted data that was meant to be kept.

By the way, all of our data files are easy to browse, copy, and paste from your Window's File Explorer.  Should you ever need to move a day, week, month, or even a year's worth of data, it's a drag and drop process.

  

Sincerely,

Gary Stern

President and Founder
Canary Labs
 
Have a question you would like me to answer?  Email askgary@canarylabs.com

Topics: Ask Gary

Jeff Knepper

Written by Jeff Knepper