IDAS redundancy

For each IDAS that you define for the system, you can specify a "failover" IDAS. If the AVEVA Historian stops receiving data from the primary IDAS, it automatically switches to the failover IDAS. The switch may take some short period of time, and some data may be lost during the transition.

Notes: Beginning with the AVEVA Historian 2023 release, IDAS redundancy is no longer supported. Any legacy IDAS already configured for failover can continue using the feature, but after connecting the IDAS to a Historian 2023 server, or upgrading it to version 2023, the failover configuration can no longer be modified.

You cannot specify a failover IDAS for an IDAS that has store-and-forward functionality enabled. These two features are mutually exclusive. Applications that require both failover and store-and-forward functionality should use a redundant Application Server with RedundantDIObjects.