What you will learn in this TP
- Apply a go-live checklist
- Set up monitoring and backup
- Troubleshoot an incident methodically
Introduction #
What you will learn in this section
- Apply a go-live checklist
- Set up monitoring and backup
- Troubleshoot an incident methodically
Context. A new server must host the internal application. You apply the team's go-live checklist, then an incident occurs: the disk fills up although nobody can find a large file.
Prerequisites: the VM from the previous labs (the app service and key-based SSH in place) · Estimated time: 90 min
Hands-on #
Guided steps, with their solution.
1. Measure the starting point
Why? A before/after audit makes hardening work measurable.
Install Lynis and note the initial hardening index and main suggestions.2. Update automatically
Why? Most compromises exploit already-patched vulnerabilities.
Apply updates, enable automatic security updates and check whether a reboot is required.3. Secure access
Why? Key-based SSH, a firewall and fail2ban form the first line of defence.
Check the SSH configuration from the networking lab, open only SSH and the application port, install fail2ban for SSH and apply sysctl hardening settings.4. Monitor
Why? An unmonitored server fails silently; node_exporter exposes system metrics for Prometheus.
Install node_exporter, check disk and memory metrics, and add a disk-space check to the health timer.5. Back up with restic
Why? restic encrypts, deduplicates and handles retention; the restore test validates the whole chain.
Initialise a local restic repository (simulating remote storage), back up/etcand/srv, apply retention and restore/srv/app/wwwto a temporary directory.6. Incident: the disk is filling up
Why? A deleted but still open file keeps its space: du no longer sees it, df does.
Run the incident scenario below, then troubleshoot: comparedfanddu, find the culprit withlsofand free the space without rebooting the server.7. Measure and document
Why? Measuring progress and writing a report turns an incident into learning for the team.
Re-run Lynis to compare the index, run the quick check from the best-practices article and write a short post-mortem (symptom, cause, resolution, preventive actions).
Difficulty level : ●●●●○ (4/5)
My progress
Sign in to track your progress and take notes. Sign in
💬 Questions about this lesson
No questions yet: be the first to ask for help or share your configuration.
Recommended Articles
Backup, monitoring and troubleshooting of a Linux server
Operate a Linux server day to day: 3-2-1 backup strategy with rsync, tar, LVM snapshots and resti...
Linux server security and hardening
Harden a Linux server: least privilege, updates, secure SSH, firewall, fail2ban, SELinux and AppA...
Linux administration best practices
Checklist for administering Linux servers: accounts and sudo, SSH, updates, systemd services, sto...
Processes, memory and performance: monitoring and troubleshooting a Linux server
Understand and control Linux processes (ps, top, signals, nice, jobs), interpret load, memory and...
Backup, Hyper-V and Windows troubleshooting
Back up and restore with Windows Server Backup (including system state and Active Directory), vir...
Windows updates and security: WSUS, Defender, BitLocker, LAPS and hardening
Maintain and secure a Windows estate: update strategy (Windows Update, WSUS, Azure Update Manager...
Storage on Linux: disks, partitions, file systems and LVM
Administer Linux storage: lsblk and blkid, GPT partitioning, ext4 and XFS, mounting and /etc/fsta...
Observability, SRE and incident management for DevOps teams
Operate what you ship: metrics, logs and traces, golden signals, SLIs, SLOs and error budgets, ac...
Networking on Linux: configuration, diagnosis, firewall and SSH
Configure and troubleshoot Linux networking: ip, ss, netplan and NetworkManager, DNS, layered dia...