System
Recovery mode ended
Recovery mode ended
Restored from Wed 24 Sep 05:45. Every step is done and every outage-sheet row is closed.
- Server down
- 06:02–06:58
- Access review
- Eszter Szabó · 07:10 · EV-9921
- Integrations
- MES adapter: Delivered · SAP S/4HANA: Not delivered · Line counter: Cannot be known
- Outage sheet
- 4 rows closed · paper ticks kept
- By
- Eszter Szabó · 07:45
- Activity
- EV-9960
Recovery code
About the recovery code
For when every administrator is locked out. Entering it gives a time-limited Administrator grant, a standing alert and a mandatory review. Vendor staff never hold it.
With administrator access and the code both lost, a local OS administrator with physical access to the host recovers through the Janus Service CLI, fully audited, which issues a new code.
If the server goes down
While the server is down every station shows the stop signal and books nothing. People take reels as needed and note reel ID, bay and every touch on the printed outage sheet.
After the restart a supervisor enters each row here as a check target. Nothing is booked from the sheet, and Janus never imports it.
If a snapshot is restored
- The administrator and Danutek decideThey name the verified snapshot and accept losing everything recorded after it.
- A maintenance-group member runs RestoreOn the host, with the OS account host IT made a member (Gábor Szabó, plant IT). Janus roles confer nothing there.
janus-service restore --snapshot 2026-09-24T14:30 # Snapshot 24.09. 14:30 (verified). Everything recorded after it is lost from Janus. # Loss acknowledged by (administrator): Eszter Szabó # Type RESTORE to continue.
- Janus starts in recovery modeThis page then leads the access review, each integration and the outage sheet.
Membership authorises running it, not accepting the lossThe run record is kept outside the databaseSnapshots: Health & snapshots