Incident desk
The first incident report should fit on one page
Collect the facts a hosting team can act on: impact, timestamps, the affected route and the changes already made.
Read the guideFIELD MANUAL
NO. 01—03
NO. 01—03
For the services you look after
The backup is a file.
Recovery is a process.
Runbooks for small-server operations. Start with a separate restore, a real request and a record of what happened.
RUNBOOK / 02
- 01 Find the known copy.
- 02 Restore somewhere else.
- 03 Check the service.
- 04 Write down the gaps.
Keep these within reach
4 practical guidesRunbook 01
Write a recovery plan you can actually use
The plan should help someone restore a service under pressure, even when its usual administrator is unavailable.
Read the guideRunbook 02
Restore it somewhere else. Then call it a backup.
A repeatable drill for a small website: recover the files, check the service and write down the gaps.
Read the guide
Runbook 03
An incident note that helps the next person
Capture the symptom, the timeline and the last change before the details disappear into a chat scroll.
Read the guide