Failed archive shifts
- Last UpdatedOct 02, 2024
- 1 minute read
One of the most common reasons for shift failure is inadequate disk space. If an archive shift fails for any reason, all further shifts are disabled and a message is sent to the log. When the cause of the failure is resolved (such as by providing more disk space), restart PI Archive Subsystem to enable archive shifts. If a failure is caused by a lack of an available archive to shift into, then register a new empty archive and enable a shift into the new archive.
Failed shifts do not cause any data loss since the archive goes into read-only mode and prevents data from being written to the archive file. All incoming data is queued in the event queue by PI Snapshot Subsystem.