We want to make our process history view redundant for operational reasons. On the server side there is no problem, add an extra server and synchronize them.
But my local Emerson office indicates that it is not possible to switch automatically between servers in the PHV program if the primary server fails.
The same issue with the embedded trending in DV operate.
Any suggestions how to solve this?
Thanks
Historical Data redundancy at the server or client level are not available. You may have two event chronicles and two continuous historians reading the same data, but they are not redundant in the sense that they will not backfill each other when they have data gaps. You can feed both event chronicles into a batch historian, but neither Process history view nor Batch history view can access the event data in that source.
As you stated, you can't have the clients, PHV or Operate trends, automatically flip while one historian or chronicle is down, and they certainly can't automatically flip when observing a period of time in the past at which the historian or chronicle was down.
Submit your idea to the Emerson User Driven Enhancement Program:
http://www.userideas-emerson.com