• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 1 reply
  • Subscribers 11 subscribers
  • Views 106 views
  • Users 0 members are here
Options
Related

How to restore store/forward without restarting servers

Dimpho Phukubje

Hi all, 

The customer is on AVEVA Historian 2020R2 P01.
All the Engines on both the AOS are stuck in Storeforward active mode, and no data is being sent to the historian.
Customer stopped, and started the Historian, but the Engines remain in store forward mode.

The plant is running, and ship is in loading progress.
Customer cannot stop/start the engines for this reason,
they need to recover from the Storeforward, in order to get the data to the historian.


Are there ways or best practices to solve this issue without restarting their servers and without impacting on the live Scada’s when the plant is in production?
Can you please assist?

Parents
  • +1

    Under normal circumstances, nothing should be required for AppEngines to switch out of store-forward except to restore the network connection. There could be some edge case where the AppEngine is "stuck", but that would be a defect. In such a case, restarting the AppEngine might cause it to recover, but that shouldn't be required.

    You mention a "ship"--not sure about your application, but if the communications is over a satellite link or another type of volatile or high-latency network there may be additional considerations--if that applies, call that out here.

    Be sure to check the SMC Log on both the AppEngine nodes and on the Historian server node to see if there is any additional information about the connections. Enabling additional log flags for the "HistorianPrimitive" (Engine) and "aahClientAccessPoint" (Historian) might give additional information. I suggest reaching out to AVEVA Tech Support to help pinpoint the problem. 

Reply
  • +1

    Under normal circumstances, nothing should be required for AppEngines to switch out of store-forward except to restore the network connection. There could be some edge case where the AppEngine is "stuck", but that would be a defect. In such a case, restarting the AppEngine might cause it to recover, but that shouldn't be required.

    You mention a "ship"--not sure about your application, but if the communications is over a satellite link or another type of volatile or high-latency network there may be additional considerations--if that applies, call that out here.

    Be sure to check the SMC Log on both the AppEngine nodes and on the Historian server node to see if there is any additional information about the connections. Enabling additional log flags for the "HistorianPrimitive" (Engine) and "aahClientAccessPoint" (Historian) might give additional information. I suggest reaching out to AVEVA Tech Support to help pinpoint the problem. 

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.