Documentation and Professionalism

Lesson 20 · Documentation and Professionalism · Download .docx

Objectives

Apply the 3-2-1 backup rule and distinguish RTO from RPO
Explain logical vs. physical network diagrams and knowledge base article structure
Demonstrate professional communication skills including active listening and escalation

Key terms

3-2-1 backup rule: 3 copies, 2 different media types, 1 offsite — the standard for resilient backup.
RTO: Recovery Time Objective — maximum acceptable time to restore a system after failure.
RPO: Recovery Point Objective — maximum acceptable data loss measured in time.
Logical diagram: Shows IP addressing, subnets, VLANs, and device roles — not physical cable placement.
Physical diagram: Shows cable runs, port assignments, and physical device locations.
Knowledge base: Searchable repository of solved problems and how-to articles for reuse.
Runbook: Step-by-step IT procedure document for performing tasks consistently.
Active listening: Full attention to user, letting them finish before diagnosing or responding.
Escalation: Routing a ticket to a higher tier when the current tier cannot resolve it.
Post-mortem: Blameless incident review documenting timeline, root cause, impact, and prevention.
CAB: Change Advisory Board — reviews proposed changes before approval to assess risk.
Password manager: Encrypted vault for storing credentials; never store passwords in plain text.

The concept

BACKUP STRATEGY

The 3-2-1 backup rule addresses three distinct failure scenarios: accidental deletion (3 copies survive), media failure (2 different media types ensure at least one works), and site disaster (1 offsite copy survives fire, flood, or theft). RTO (Recovery Time Objective) defines the maximum acceptable downtime — how long the business can operate without the system. RPO (Recovery Point Objective) defines the maximum acceptable data loss — how old the restored data can be. A 4-hour RPO means backups must run at least every 4 hours.

NETWORK DOCUMENTATION

A logical network diagram focuses on IP addressing schemes, subnet boundaries, VLAN assignments, and the logical roles of each device. It answers 'how does traffic flow?' A physical network diagram shows the physical cable runs between devices, patch panel ports, switch port assignments, and the physical location of equipment. A rack elevation diagram shows what equipment occupies each rack unit.

KNOWLEDGE BASE ARTICLES

A quality knowledge base article contains: clear problem description (symptoms the user sees), environment details (OS version, affected application), step-by-step resolution instructions, and verification steps (how to confirm the fix worked). Articles must be reproducible by any technician without prior knowledge of the issue.

PROFESSIONAL SKILLS

Active listening means giving the user your full attention, allowing them to complete their explanation before proposing solutions — users often reveal critical diagnostic details when not interrupted. Escalation routes tickets to a higher tier when the current tier lacks the capability to resolve the issue. A blameless post-mortem documents the incident timeline, root cause, business impact, resolution steps, and preventive measures — focusing on systems and processes rather than assigning individual blame. Passwords and secrets must always be stored in a password manager or enterprise vault — never in plain text files, spreadsheets, or support tickets.

Worked examples

Example 1: A hospital IT team must define RTO and RPO for the patient records system. Business analysis: the system cannot be down more than 30 minutes before clinical operations are impacted (RTO = 30 min). Losing more than 15 minutes of patient data is unacceptable (RPO = 15 min). These objectives drive the infrastructure decision: a hot standby failover cluster with synchronous replication and backups every 15 minutes.

Example 2: A user reports 'the internet is broken.' Poor response: immediately ask for a ticket number. Active listening approach: acknowledge the report, let the user fully describe what they can and cannot do, ask clarifying questions (when did it start? what were you doing? can you open any sites?). This reveals that only their browser fails — pointing to a browser/DNS issue rather than a network outage.

Common mistakes

Confusing RTO (downtime tolerance) with RPO (data loss tolerance) — they measure completely different things.
Treating RAID 1 as a backup — RAID 1 protects against drive failure, not ransomware or accidental deletion.
Writing knowledge base articles with technical jargon that only senior engineers understand.
Interrupting users to propose solutions before they finish explaining — missing key diagnostic details.
Storing passwords in support tickets or spreadsheets — any system breach exposes all credentials at once.

Self-check

Try each one before you look. A miss here costs nothing and tells you exactly what to reread.

1. The 3-2-1 backup rule states:

2. RTO (Recovery Time Objective) measures:

3. A logical network diagram shows:

4. Active listening in IT support means:

5. A post-mortem is:

Canvas is the official record. This companion enhances the PGCC curriculum; it does not replace it. Last name and class year only. Students with a 504 plan or IEP: your accommodations apply.

↑ Back to top