Applies To:
  • CitectSCADA 3.00

With network restart there is a problem with trend redundancy. It has to do with the fact that a redundant trend server in phase one asks the other trend server for data when it comes up. However the other trend server doesn't know how to act when it is told to shutdown in the second phase. Sometimes it shutsdown and data tranmission is interupted and sometimes it stays up transmitting the data and not shutting down. This seems to be a problem as the trending data will be lost during that ambiguous period. Is there a way to work around this problem? 

CIT has confirmed this to be a problem in Citect for Windows version 3.00. We are researching this problem and will post new information here as it becomes available.

However the workaround is to set NetworkIgnore parameter for the trend servers and employ a manual shutdown and restart procedure which will maintain one of the trend servers up and running while the other one is shutdown.: