Catch a failed MariaDB backup before it matters
Every morning, WebRun opens the MariaDB management console, checks every scheduled backup job's completion status and size against recent runs, opens a Trello card for anything failed or undersized, and pings the DBA on WhatsApp.
- No credit card
- Under $0.01 per run
- Cancel anytime
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
mariadb.comin a real browser with your saved login - no setup, no API keys. -
1
MariaDB - check backup job status
mariadb.com
WebRun opens MariaDB to check backup job status. - Open the MariaDB management console and list scheduled backup jobs
- Check each job's completion status and backup size
- Note any backup that failed or came back smaller than usual
Done when Every scheduled backup job has a checked status.
-
2
Trello - open a card for a failed backup
trello.com How to Automate Trello
WebRun opens Trello to create a card for a failed backup. - Open a card for any backup that failed or looks undersized
- Attach the job name, the database, and the error if there is one
Done when A Trello card exists for every failed or undersized backup.
-
3
WhatsApp - ping the DBA
whatsapp.com How to Automate WhatsApp
WebRun sends a WhatsApp message to ping the DBA. - Message the DBA the moment a backup fails
- Name the database and the job so they can act quickly
Done when The DBA has a WhatsApp message for every failed backup.
How do I get alerted when a MariaDB backup job fails?
WebRun checks every scheduled MariaDB backup job each morning, reading its completion status and size against recent runs. A failed or undersized backup gets a tracked Trello card with the job and database named, and a direct WhatsApp message to the DBA, so a broken backup gets caught the same day, not discovered during a restore.
- Failed backups get caught the same day, not during a restore
- Every failure comes with a tracked Trello card, not just a log entry
- Undersized backups get flagged even when the job reports success
Built for database administrators · platform engineers · IT operations · backend engineering teams
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 re-run the backup or fix the job on its own?
No. WebRun only reports the failure and tracks it. Re-running a backup job or fixing the underlying issue is left to a human.
What counts as an undersized backup?
A completed backup that's noticeably smaller than its recent average, which can signal a partial backup even when the job reports success.
What happens once the backup succeeds again?
It checks the latest backup status each morning, so a job back to normal doesn't stay flagged past the day it recovers.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.