What's the correct approach for redundant Historians and a demanding Historian Client Web?

Hi everyone,

I've set up two redundant Historians and I look at one of them with the Historian Trend Client, the Historian Query Client and the Historian Client Web.

Now I shut down the one I am querying.

The Historian Trend Client automatically points to the partner Historian as soon as it doesn't reach the first Historian.

But what about the other tools, Query and Client Web?
According to documentation:
When the primary historian is unavailable, a Historian Client automatically switches over to the configured partner historian. The client remains connected to the partner historian, even when the primary historian becomes available again. A Historian Client switches back to an available primary historian if it fails to connect to the partner or during a new attempt to connect to the primary historian, such as when restarting Trend.

A Historian Client? It seems to be only the Historian Trend Client. Any hints or suggestions on this one?

Thanks
Peter

Parents Reply Children
No Data