Database Backup Verification

← Back to gallery

Database Backup Verification

Incident ManagementAWS API - RDSPagerDutySlack

This Flow verifies on a daily schedule that every monitored RDS database has a recent backup, comparing the newest snapshot against each database's expected backup window. When a backup is overdue or missing, it creates a PagerDuty incident with the details — which database, the last known backup time, and how overdue it is — and posts a Slack alert tagging the on-call DBA. Each stale backup only pages once, and successful verifications are recorded in memory. If the check itself fails, the error is reported to Slack, so verification never fails silently.

Time (built-in)Schedule

Daily Backup Check

AWS API - RDSDescribe DB Snapshots

Fetch Recent Backups

Business logic (built-in)Transform

Evaluate Backup Freshness

Business logic (built-in)Condition

Backup Fresh?

Memory (built-in)Memory Set

Record Success

PagerDutyCreate Incident

Create PagerDuty Incident

PagerDutyGet On-Call Users

Get On-Call DBA

SlackLookup User by Email

Lookup DBA in Slack

SlackSend Text Message

Post Backup Alert

Errors (built-in)Handle Error

Catch Check Errors

SlackSend Text Message

Post Check Failure

Collections (built-in)Explode

Each Monitored Database

Memory (built-in)Memory Set

Mark Alerted

Business logic (built-in)Condition

Not Alerted Yet?

Copy

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.

Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.