广告广告位招商联系 ads@iaunion.comA5 · 728×90(移动端 320×100) · 参考价 ¥300/月了解详情 →

【Editorial】Store-and-forward after a week-long outage: how do you backfill without drowning the historian?

Started by FPGA_ARM_Linux · 2026-11-15 02:00 UTC · 18 views · 1 replies
F Member
【Editorial Discussion】

An edge node that correctly stores data during a network outage still has to get that data into the historian when the link returns. A week of high-rate tags replayed at full speed can overload the server, scramble order, or hide a live outage under a backfill storm. “We have store-and-forward” is not the same as a tested replay policy.

1) Decide the order and the rate before the outage happens. Oldest-first versus newest-first, a bandwidth cap, and whether live data has priority over backfill should be written down. An unbounded replay will look like a historian incident.

2) Duplicate keys and overlapping timestamps need a rule. Replayed data that meets live data in the middle of the gap, or a node whose clock jumped, can create two values for one timestamp or an apparent step backwards. The identifier of the source and the quality or origin flag should survive the replay.

3) Not every tag deserves the same retention. Fast cyclic data, events, and alarms may have different gaps that are acceptable. A policy that stores everything at full rate for a week can fill the edge disk and still miss the event you cared about if the disk was already wrapping.

4) Test the failback, not only the failover. A planned disconnect of realistic length, followed by replay under production-like historian load, is the only way to know whether the policy works.

Open question: after a long outage, do you cap replay, drop the oldest, or stall live updates until the gap is closed? Have you filled a historian or an edge disk this way? Please share the policy that survived contact with a real gap.
Z Member
断网一周后的回补,关键是先定策略再开闸。建议实时数据优先、回补限速分批:报警、事件类先回补,高速循环数据按时间分片、错峰回放,避免瞬间写满历史库。去重要靠源标识加时间戳加质量位三者联合判重,同一时间戳只保留一条,回补数据打上来源标记,方便事后审计。断网时长要设上限,超过保留期的低价值点直接丢弃并留档说明。最关键的是定期做真实时长的断网演练,测回补速率、磁盘占用和查询是否受影响,而不是只测通断。
广告广告位招商联系 ads@iaunion.comA6 · 728×90(移动端 320×100) · 参考价 ¥200/月了解详情 →
Log in or register to reply.