hetzbot-backup

Trigger on-demand restic backups on hosts defined in hosts.tfvars.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-backup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hetzbot-backup
Source: https://github.com/tomspiegl/hetzbot/tree/main/skills/ops/backup
Command: npx skills add https://github.com/tomspiegl/hetzbot --skill hetzbot-backup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Force a backup run on a specified host to ensure a fresh data snapshot.

Core Features & Use Cases

  • On-demand backup trigger for hosts, independent of the nightly timer.
  • Baseline snapshot count before the backup and verification of a new snapshot.
  • Safe remote execution and validation with clear recovery guidance for failures.
  • Use Case: Before a risky operation like tofu destroy or manual fixes, to capture current state.

Quick Start

Trigger a backup on a chosen host by confirming the host from the list and initiating the on-demand backup workflow.

Frequently Asked Questions about hetzbot-backup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trigger a restic backup on demand before a risky server operation?

Trigger an on-demand restic backup by selecting a reachable host and initiating the backup workflow, which captures a baseline snapshot count and verifies the new snapshot creation. This ensures a fresh data snapshot independent of the nightly timer.

Can I force a database pg_dump backup outside of the scheduled nightly timer?

Yes, you can force a database pg_dump backup on demand by executing the remote backup-now.sh script on a specified host. The process coordinates baseline capture, remote execution, and post-run verification to validate the new snapshot.

What is the best way to verify an SSH backup snapshot was created successfully?

The best way to verify an SSH backup snapshot is through post-run verification, which checks the new restic snapshot against a baseline snapshot count captured before the backup run, providing clear recovery guidance if failures occur.

Does this on-demand backup approach work with hosts defined in hosts.tfvars?

Yes, the on-demand backup works with any reachable host defined in hosts.tfvars, allowing you to select a target host and trigger a fresh data snapshot whenever a validation is required before risky operations.

Why does my forced host backup fail and how do I recover?

A forced host backup may fail during remote execution or restic snapshot creation; the workflow includes post-run verification with clear recovery steps and guidance to address failures and ensure data consistency.

When do I need to force a backup run instead of waiting for the nightly schedule?

You need to force a backup run when a risky operation like tofu destroy or manual fixes is about to occur, ensuring you capture the current state and validate a fresh data snapshot before proceeding.