• State Not Answered
  • Replies 1 reply
  • Subscribers 17 subscribers
  • Views 18 views
  • Users 0 members are here
Options
Related

Historian Redundant Servers

Dimpho Phukubje

Using AVEVA Historian 2017 Update 3 SP1 P01. The historian servers are redundant. However, the primary shows the trends as license is activated on it, the secondary server goes into demo mode, license tag violation and shows no trends. Disconnected the eternet cable and so the clients are not getting the trend because they are pointing to primary server.  Is the secondary server supposed to automatically pick up the license and be active when the primary server goes down? Or is it possible to force the license manager to release the licenses? 


  • 0

    Is it a question about a partner historian configuration? If it is, then you have just two independent historian servers having a system parameter pointing to its partner. They get licensed independently and accepting the same data duplicated to both from the application server engine. A trend client is just switching to the other one if it cannot reach the primary historian and vice versa. No license release happens just because some trend client fails to reach any of them. Theoretically if the licenses are issued by a license server in your network and one of the historians really goes down, then the license server should release all licenses previously acquired by that stopped historian after some timeout. The running historian is expected to automatically re-acquire that license after some time. If that license release/re-acquisition never happens (assuming that primary historian is completely down), I would suggest contacting the AVEVA Technical support for further investigation.