II.
Workflow overview
Reference · liveworkflow:backup-recovery-drill
Backup Recovery Drill overview
Validates database backup integrity and disaster-recovery procedures through controlled restore exercises — measuring RTO/RPO, documenting gaps, and updating runbooks. Excludes daily backup scheduling.
Attributes
displayName
Backup Recovery Drill
workflowKind
operational
triggerType
scheduled
typicalCadence
quarterly
complexity
cross-team
description
Validates database backup integrity and disaster-recovery procedures
through controlled restore exercises — measuring RTO/RPO, documenting
gaps, and updating runbooks. Excludes daily backup scheduling.
Outgoing edges
applies_to_domain4
- domain:databases·DomainDatabases
- domain:infrastructure·DomainInfrastructure
- domain:databases·DomainDatabases
- domain:infrastructure·DomainInfrastructure
involves_role6
- role:database-administrator·RoleDatabase Administrator
- role:platform-engineer·Role
- role:incident-commander·RoleIncident Commander
- role:database-administrator·RoleDatabase Administrator
- role:platform-engineer·Role
- role:incident-commander·RoleIncident Commander
performed_by_org_unit4
- org-unit:database-team·OrgUnitDatabase Team
- org-unit:platform-team·OrgUnitPlatform Team
- org-unit:database-team·OrgUnitDatabase Team
- org-unit:platform-team·OrgUnitPlatform Team
requires_skill_area4
- skill-area:postgres-tuning·SkillAreaPostgres Performance Tuning
- skill-area:chaos-engineering·SkillAreaChaos Engineering
- skill-area:postgres-tuning·SkillAreaPostgres Performance Tuning
- skill-area:chaos-engineering·SkillAreaChaos Engineering
triggers_responsibility4
- responsibility:runbook-authoring·ResponsibilityRunbook authoring
- responsibility:respond-incidents·ResponsibilityRespond to production incidents
- responsibility:runbook-authoring·ResponsibilityRunbook authoring
- responsibility:respond-incidents·ResponsibilityRespond to production incidents
Incoming edges
follows_workflow1
- stack-profile:disaster-recovery·StackProfileDisaster Recovery (Terraform, Kubernetes, Prometheus, PostgreSQL, S3)