Automated Redis Backup Coverage Checks
Every morning, WebRun signs in to Redis Cloud, opens each database across your subscriptions, reads the backup schedule, the last backup time and the persistence setting, marks any database without a backup from overnight, texts the on-call engineer through Twilio, and posts the full coverage list to Microsoft Teams.
How do I check every Redis database has a recent backup?
Every morning, WebRun signs in to Redis Cloud, opens each database in your subscriptions, and reads its backup schedule, last backup time and persistence setting. It posts a coverage list to Microsoft Teams and texts you through Twilio when a database has no fresh backup, so gaps surface before an incident.
- A database with no fresh backup is found on a quiet Tuesday, not during an incident
- Every database has a dated pass or fail each morning
- No backup setting is ever changed by the run
Built for platform engineers · SRE teams · DevOps · data infrastructure teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
cloud.redis.ioin a real browser with your saved login - no setup, no API keys. -
1
Redis - read last backup on every database
redis.io
WebRun opens Redis to read last backup on every database. - Sign in to Redis Cloud and list every subscription
- Open each database and read its backup schedule and last backup time
- Note the persistence setting and where the backup is stored
- Mark any database whose last backup is older than the schedule promises, or that has no backup configured at all
- Change no setting. WebRun reads the configuration and leaves it exactly as it found it
Done when Every database has a last backup time and a pass or fail against its schedule.
-
2
Twilio - text the on-call engineer
twilio.com
WebRun opens Twilio to text the on-call engineer. - Text the on-call engineer's own number when any database fails the check
- Name the database, its subscription and how old the last backup is
- Send nothing on a morning when every database passes
Done when A missing backup has reached the on-call engineer's phone.
-
3
Microsoft Teams - post the coverage list
microsoft.com
WebRun opens Microsoft Teams to post the coverage list. - Post the full coverage list to your platform channel
- Put failing databases at the top with the age of their last backup
- Show the passing databases underneath so the check is visibly complete
- Note any database where persistence is off, even if a backup exists
Done when The channel shows today's backup coverage for every database.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it change any backup settings?
No. WebRun reads the schedule, the last backup time and the persistence setting, then reports. Every configuration change stays with an engineer.
Does it trigger a backup when one is missing?
No. It reports the gap and leaves the fix to a human, so nothing is written to a live database by the run.
What if a database is meant to have no backup?
Mark it as exempt once and WebRun records it as expected, so the daily list only raises databases that genuinely should be covered.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.