Legacy features
- Last UpdatedFeb 27, 2025
- 1 minute read
If you install AVEVA Historian from an earlier version, you may still use some legacy features when
-
Data is collected by previous Historian versions
-
Events are stored in A2ALMDB
-
Classic Event subsystem is used for notifications
-
Classic Storage subsystem was used for classic IDASes.
Note that the Classic Storage subsystem is now replaced by the Classic Data Redirector process (aahStoreSvc.exe), which performs the same functionality.
This table compares legacy features with upgraded features in Historian 2017:
|
Legacy feature |
Upgraded feature in Historian 2017 |
|---|---|
|
Classic storage subsystem |
The current storage subsystem. See Manage data storage. |
|
Classic events subsystem |
Events are managed through the Alarms and Events subsystem. |
|
A2ALMDB |
New events are written to special history blocks for events. For more information, see Manage partitions and history blocks. |