Schedule archive shifts
- Last UpdatedOct 02, 2024
- 1 minute read
Users can now configure PI Archive Subsystem to automatically shift historical archives at a specific time duration rather than having PI Archive Subsystem shift based on remaining archive space, or by manually forcing a shift. The result of this is fixed time archives.
With daily duration, shifts happen at midnight every day. With weekly duration, shifts happen at the midnight of Sunday. With monthly duration, shifts happen at midnight of the first day of every month. In regions where daylight savings time occurs at midnight, for the Spring transition, the shift time will be at 1:00:00 daylight saving time. For the Fall transition, the shift time will be at 0:00:00 standard time. Natural shifting is just allowing the shift to occur automatically when the archive is full.
When the Archive_AutoArchiveFileSize tuning parameter is set, the new primary archive's size will be based on this value. When it is not set, PI Archive Subsystem calculates the new primary archive's size based on past data rate and the shift duration, so that the archive can accommodate the expected amount of data.
In collective environments, scheduled shift can be configured on the primary server which applies to all members. Secondary members will shift based on the primary server's time zone. As in earlier versions, future archives are still considered monthly archives. In a collective, future archives' start and end times are now based on the primary's time zone.
Note: If you are upgrading an existing PI Collective, you will need to upgrade all the secondary members before upgrading the primary server. For more information see Scheduled archive shifts in collective manager.