Great question Joe.  Typically, when I hear 'real time backup' what I think of is a redundant historian, not a disaster recovery solution or failover.  Remember, Canary moves data from the original data source, through the appropriate Canary Collector (think OPC UA, MQTT, API, etc) and prepares it for our Sender Service.  The Sender Service is then targeted towards the Receiver and Canary Historian. 

A unique feature of our Sender is that you can send multiple streams of data from a single Sender.  This allows you to target multiple Receiver/Historian servers.  So, if your typical Sender configuration looks like this:

Historian: CanaryHistorianPrimary

you would simply add a comma and the next historian name or IP address....

Historian: CanaryHistorianPrimary, CanaryHistorianRedundant

The result is two independent data streams, one to each historian.  The Sender is even capable of managing each stream independently.  This means if the primary historian is unavailable, the Sender will buffer that data while still streaming the other data feed to the redundant historian.  All of this happens automatically without any configuration or admin involvement.

Does that answer your question?