Learn about Location5 (data archiving and history recovery)
- Last UpdatedAug 19, 2025
- 1 minute read
- PI System
- Interfaces
The Location5 attribute configures exception reporting and the handling of events with duplicate timestamps. For output points, it configures how events are recovered from Data Archive to an RDBMS. For details about recovery, see Learn about how to recover historical data in this document.
Tags and queries that include PI annotations bypass exception reporting and are written directly to the archive, regardless of their Location5 attribute setting.
Note that the interface also performs recovery during startup in real-time mode, to ensure that it captures any events that occurred during its downtime.
Input points
To configure handling of out-of-order data for an input point, set Location5 as follows:
|
Value |
Description |
|---|---|
|
0 |
Enable standard exception reporting and out-of- order data handling for a tag. If the archive already contains an event with the same time- stamp as the incoming event, the archived event is not replaced with the incoming event. |
|
1 |
Disable exception handling and send all incoming values to the snapshot. For out-of-order data, existing events are replaced and new events are added. |
|
2 |
Archive all incoming out-of-order values. Be aware that if you set Location5 to 2 , there can be multiple events with the same timestamp. |
|
3 |
For the tag distribution strategy, forward to PI only newer events than PI snapshot. |
|
4 |
Enables the full sync mode. See section: Full synchronization of time series from RDB tables to PI Data Archive. |