database-reliability

# Database Reliability Engineering Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. <!-- dual-compat-start --> ## Use When - Database reliability engineering: SLOs for databases, operational runbooks, change management, capacity planning, backup verification, incident response, and monitoring strategies for production MySQL. Use when setting up production database... ## Do Not Use When - The request concerns logical schema design without recovery, availability, or operational risk; use `database-design-engineering`. - The task asks for a vendor command copied into production without an approved maintenance window, tested backup, and rollback path. ## Required Inputs | Input | Required | Why it matters | |---|---|---| | Business RPO and RTO by datastore | yes | Sets backup frequency and recovery architecture | | Topology, engine version, and data size | yes | Constrains replication, restore, and failover procedures | | Backup, retention, encryption, and access configuration | yes | Establishes whether recoverable copies exist | | Incident history and capacity trends | conditional | Reveals recurring failure and saturation modes | ## Workflow Translate RPO and RTO into controls, map failure modes, inspect backup and replication paths, perform a controlled restore, validate recovered data and application behavior, then record gaps, owners, and the next exercise date. ## Quality Standards Backup presence is not recovery evidence. Claims re...