Trend Backfill Resilience

Hi all, I'm looking for some clarification on how Citect handles interruptions to the backfill process, i.e. when a server is shutdown during a backfill operation. I know in earlier versions this would leave permanent gaps in the trend history on the server being backfilled (ref. TN5933), but is this still the case?

Parents
  • Hi Philip,

    This is still the same in 2018R2.
    Depending on which server you shutdown during the synchronization you could end up with gaps.

    If ServerPri is the server which was running and you backfill to ServerStby, you have to wait for ServerPri to empty the TrnRdn.GapFillDelayQue ” outstanding work to process
    TrnRdn.GapFillSentQue ” items awaiting a response from the redundant server

    Stopping the ServerPri while these queus are not fully processed will lead to gap in trend data on ServerStby.
    Stopping ServerStby while backfilling should not really be an issue as long as ServerPri keeps running.

    You can use ServerGetProperty with SyncStatus and SyncProgress to check on the progression during backfill.
Reply
  • Hi Philip,

    This is still the same in 2018R2.
    Depending on which server you shutdown during the synchronization you could end up with gaps.

    If ServerPri is the server which was running and you backfill to ServerStby, you have to wait for ServerPri to empty the TrnRdn.GapFillDelayQue ” outstanding work to process
    TrnRdn.GapFillSentQue ” items awaiting a response from the redundant server

    Stopping the ServerPri while these queus are not fully processed will lead to gap in trend data on ServerStby.
    Stopping ServerStby while backfilling should not really be an issue as long as ServerPri keeps running.

    You can use ServerGetProperty with SyncStatus and SyncProgress to check on the progression during backfill.
Children
No Data