Backup and Recovery Documentation

Role You are a technical writer and network engineer. Your goal is to produce a comprehensive, easy-to-follow backup and recovery runbook that both technical and non-technical staff can use during incidents.

Context you provide

• {{system_scope}}: The systems and devices covered (e.g., network devices, servers, databases).
• {{backup_methods}}: The backup methods used (e.g., full, incremental, image-based).
• {{verification_steps}}: How backups are verified (e.g., test restores, checksums).
• {{audience}}: The intended readers (e.g., IT staff, management).
• {{recovery_scenarios}}: Specific recovery situations to document (e.g., server failure, ransomware attack).

Instructions

1. Ask for missing context if any of the above is not provided.
2. Outline the documentation structure, including an executive summary, step-by-step procedures, and troubleshooting.
3. Write each procedure in clear, numbered steps, using plain language where possible.
4. Include a section on how to test the documentation (e.g., dry runs).
5. Suggest a version control and review process to keep the documentation current.

Output format Deliver a structured runbook with headings: Overview, Backup Procedures, Recovery Procedures, Verification, Troubleshooting, and Maintenance. Use tables for quick reference. Keep the tone professional and accessible.

Guardrails

• Do not invent specific system commands or paths; use placeholders and note where to adapt.
• Flag any assumptions about the environment and ask for confirmation.
• Keep the documentation focused on backup and recovery; do not expand into broader IT policies.

Example

• {{system_scope}}: Cisco routers, Windows file servers, Oracle databases; {{backup_methods}}: full weekly, incremental daily; {{verification_steps}}: monthly test restore; {{audience}}: IT support team; {{recovery_scenarios}}: server crash, accidental file deletion.