Storage: capacity, performance, and recovery
Six lessons, 30 questions, and six cases on storage interfaces, capacity, performance, durability, recovery, and RUN handover.
Objectives and progression
A technical course with six modules and fictional APS scenarios. Learn to map storage, diagnose capacity and latency, assess shared writing, and recover applications using functional criteria. Includes selected Linux and AWS examples, primary references, and an internal assessment of 24 decisions in 60 minutes.
Audience: APS L2/L3, Linux administration, infrastructure, cloud teams, and technical managers.
Prerequisites: Linux, file, and application fundamentals; calculation assumptions are provided.
300 estimated study minutes
- Choose the interface and identify storage actually used by the application.
- Distinguish bytes, inodes, layers, and physical pool headroom.
- Relate IOPS, size, throughput, queue, and latency using explicit units.
- Distinguish redundancy, persistence, and write authority.
- Define a recoverable point and distinguish technical restore from functional acceptance.
- Prepare cutover, recovery, decommission, and operational autonomy.
Modules
- Interfaces and dependencies
- Capacity and growth
- Performance and measurement
- Durability and coordination
- Snapshots and recovery
- Migration, FinOps, and RUN
Continue learning
References and version
DR Storage 2026-09; selected Linux and AWS storage behavior
- EBS volume types and workload fit · 2026-09-30
- EBS I/O size, IOPS, throughput and latency · 2026-09-30
- EBS incremental point-in-time snapshots · 2026-09-30
- Linux block I/O statistics · 2026-09-30
- Linux device mapper thin pools · 2026-09-30
- Extend filesystem after EBS volume growth · 2026-09-30
- EBS snapshot consistency and cached data · 2026-09-30
- EC2 temporary instance store · 2026-09-30
- S3 object storage and consistency · 2026-09-30
- EBS shared block access and clustered filesystems · 2026-09-30
- Linux fsync data, metadata and directory distinction · 2026-09-30
- Filesystem capacity and inode observations · 2026-09-30
- Linux software RAID state and redundancy · 2026-09-30
- EFS shared file storage · 2026-09-30
- EBS restore initialization and performance · 2026-09-30
- EBS snapshot deletion and retained data · 2026-09-30
- EBS encryption and KMS dependencies · 2026-09-30
- AWS Backup restore testing and validation · 2026-09-30
- EC2 instance store lifecycle · 2026-09-30
- findmnt mounted filesystem inspection · 2026-09-30
- Linux unlink and open file lifetime · 2026-09-30
- Define recovery objectives for downtime and data loss · 2026-09-30
What you will explore
0 / 6Interfaces and dependencies
Choose the interface and identify storage actually used by the application.
Capacity and growth
Distinguish bytes, inodes, layers, and physical pool headroom.
Performance and measurement
Relate IOPS, size, throughput, queue, and latency using explicit units.
Durability and coordination
Distinguish redundancy, persistence, and write authority.
Snapshots and recovery
Define a recoverable point and distinguish technical restore from functional acceptance.
Migration, FinOps, and RUN
Prepare cutover, recovery, decommission, and operational autonomy.