Automated Contabo Snapshot Coverage Checks
Every night, WebRun signs into the Contabo control panel, checks every VPS for a recent snapshot or backup, works out how old the newest recovery point on each one is, logs the coverage in Google Sheets, and posts to Microsoft Teams the servers that could not be restored today.
How do I check every server has a recent backup or snapshot?
Every night WebRun signs into the Contabo control panel and checks every VPS for a recent snapshot or backup, working out how old the newest recovery point on each one is. It logs coverage in Google Sheets and posts to Microsoft Teams the servers that could not be restored today, ranked by importance.
- Servers with no recovery point are named the same night
- Recovery point age is tracked per server instead of assumed
- Object storage filling up is caught before it stops the next backup
Built for sysadmins · DevOps engineers · hosting resellers · small IT 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
my.contabo.comin a real browser with your saved login - no setup, no API keys. -
1
Contabo - check snapshot and backup age
contabo.com
WebRun opens Contabo to check snapshot and backup age. - Sign in to the Contabo control panel and list every VPS on the account
- Open each instance and read the date of its most recent snapshot
- Check whether a backup is enabled on the instance and when it last ran
- Work out the age of the newest recovery point per server
- Rank the servers by the importance tag you set, so a production box with no snapshot outranks a test box
- Note the object storage buckets holding backups and whether they are filling up
Done when Every VPS has a recovery point age and a rank recorded.
-
2
Google Sheets - log nightly coverage
google.com
WebRun opens Google Sheets to log nightly coverage. - Append tonight's coverage row per server: name, snapshot date, backup state and recovery point age
- Keep the history so a server drifting out of coverage is visible over weeks
- Update the count of servers with no recovery point in the last seven days
- Highlight rows where the age crossed the threshold you set
Done when Tonight's coverage is recorded for every server in the sheet.
-
3
Microsoft Teams - post the servers with no recovery point
microsoft.com
WebRun opens Microsoft Teams to post the servers with no recovery point. - Post to the infrastructure channel the servers with no recent snapshot or backup
- Put the highest ranked servers first, with the age of their newest recovery point
- Note object storage nearing its limit, since that stops future backups
- Say clearly when every server is covered, so a clean night is still reported
Done when Whoever is on call knows which servers could not be restored today.
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 create or delete snapshots itself?
No. WebRun reads the control panel and reports what recovery points exist. Taking a snapshot, enabling a backup or deleting an old one stays with your engineer, because each one costs storage.
Can it restore a server?
No, and it never will. Restoring overwrites a running machine, so it is deliberately outside what this run does. WebRun only tells you whether a restore would be possible.
How does it decide which servers matter most?
From the importance tag you set once per instance. A production server with no snapshot is posted above a test box with the same gap, so the on-call engineer reads the riskiest line first.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.