Automated Hetzner Backup Coverage Checks
Every night, WebRun signs in to Hetzner, walks every project and server, checks when each last got a snapshot or backup, posts the full coverage table to Microsoft Teams, and pings you on Telegram with the servers that have no recent protection at all.
How do I check that every Hetzner server has a recent backup?
WebRun checks every Hetzner server each night for a recent snapshot or backup, walking every project in your account. It posts a coverage table to Microsoft Teams showing days since each server was last protected and pings you on Telegram naming any server that is unprotected, well before a restore is needed.
- Unprotected servers surface nightly, not after a failed restore
- Every server carries a days-since-backup number
- A server with backups switched off is called out by name
Built for infrastructure owners · sysadmins · DevOps teams · hosting providers
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
www.hetzner.comin a real browser with your saved login - no setup, no API keys. -
1
Hetzner - check snapshot and backup dates
hetzner.com
WebRun opens Hetzner to check snapshot and backup dates. - Open Hetzner and list every project and the servers inside it
- For each server, read whether backups are enabled and when the last backup ran
- Read the newest snapshot date for the server and any attached volumes
- Mark a server unprotected when its newest snapshot or backup is older than your threshold
Done when Every server carries a last-protected date and a pass or fail.
-
2
Microsoft Teams - post the coverage table
microsoft.com
WebRun opens Microsoft Teams to post the coverage table. - Post the coverage table to your infrastructure channel, grouped by project
- Show each server with its last backup date, last snapshot date, and days since
- Put failing servers at the top and note which have backups switched off entirely
- Compare against last night so newly failing servers are called out
Done when Tonight's coverage table is in Teams with failures first.
-
3
Telegram - alert on unprotected servers
telegram.org
WebRun opens Telegram to alert on unprotected servers. - Send a short alert naming the servers with no recent snapshot or backup
- State how many days each has been unprotected and which project it sits in
- Stay quiet when every server passes, so the message means something
- Leave taking snapshots and enabling backups to you. WebRun never changes a server
Done when You know before morning which servers are unprotected.
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 snapshots or turn backups on?
No. WebRun only reads backup and snapshot dates and reports the gaps. Creating a snapshot, enabling backups, or deleting an old one stays with your team, since each one costs money or storage.
How old is too old?
You set the threshold, commonly 24 hours for backups and 7 days for snapshots. Any server past it is marked unprotected on that night's run.
Does it message anyone outside the team?
No. The coverage table goes to your Microsoft Teams channel and the alert to your own Telegram. Nothing leaves your organisation.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.