Automated Couchbase Backup Verification
Every morning, WebRun opens your Couchbase cloud console, goes through each cluster and bucket, checks whether the scheduled backup ran overnight and how old the newest restore point is, records the state in Airtable so the history is visible, and opens a Trello card for any bucket whose backup was skipped or failed.
How do I verify my database backups actually completed?
WebRun opens your Couchbase console every morning and checks whether each bucket's scheduled backup actually ran, recording how old the newest restore point is. It logs the state in Airtable and opens a Trello card for any bucket that was skipped, so a gap is found before a restore is needed.
- A skipped backup is known the next morning, not on restore day
- Every bucket's restore point age is recorded daily
- Missed backups become owned cards instead of chat messages
Built for database administrators · platform engineers · SRE teams · data owners
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.couchbase.comin a real browser with your saved login - no setup, no API keys. -
1
Couchbase - check each bucket's backup
WebRun opens Couchbase to check each bucket's backup. - Open the Couchbase cloud console and list every cluster on the account
- For each cluster, list the buckets and their backup schedules
- Check whether last night's scheduled backup ran, failed, or never started
- Record the time of the newest restore point for every bucket and how old it is in hours
Done when Every bucket has a backup status and the age of its newest restore point.
-
2
Airtable - record the backup register
WebRun opens Airtable to record the backup register. - Open the backup register base in Airtable
- Add today's row per bucket: cluster, bucket, scheduled time, actual backup time, status
- Keep previous days so a bucket that quietly stopped backing up is easy to spot
- Highlight any bucket whose newest restore point is older than its schedule allows
Done when Today's backup state for every bucket is recorded in Airtable.
-
3
Trello - raise a card for a missed backup
WebRun opens Trello to raise a card for a missed backup. - Open the database operations board in Trello
- Create a card for each bucket whose backup failed or never ran, naming the cluster and the gap in hours
- Put the oldest restore point at the top of the card so the risk is obvious
- Skip buckets that already have an open card from a previous run
Done when Every missed backup has a card on the operations board.
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
Does it start a backup or run a restore?
No. WebRun only reads the backup state and reports it. Triggering a backup or restoring a bucket stays with your database team, where an accidental restore cannot happen.
How does it catch a backup that failed silently?
It compares the age of each bucket's newest restore point against its schedule. A bucket that should back up nightly but has a restore point 40 hours old is reported, even if nothing showed an error.
Does it change any cluster settings?
No. It reads clusters, buckets, and backup schedules and writes only to your Airtable register and Trello board. Nothing in Couchbase is modified.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.