Afternoon Brian and welcome!

We can.  Best way to achieve this is to add the Canary Module for Ignition to the redundant Ignition server, and have it point to the same Canary Historian with the same DataSet name; basically use the exact same configuration for both servers.

Should the primary Ignition server fail and the secondary begins logging, our Receiver service will immediately pick up the new stream from the secondary Ignition server and write that data to the same tag name as the primary Ignition server writes to.