hetzbot-restore

Restore a service's DB and /srv data from restic snapshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restoring a service's DB and /srv data from restic snapshots is error-prone and risky without guardrails. This skill provides a controlled, per-service recovery workflow that minimizes downtime and protects data.

Core Features & Use Cases

  • Per-service restoration from restic snapshots on a single host, not a full host rebuild.
  • Automatic pre-restore backups, stop/start orchestration, and post-restore verification.
  • Safe rollback capability with explicit prompts and auditable state changes.

Quick Start

Use the hetzbot-restore skill to restore a service on a host from a specific restic snapshot.

Frequently Asked Questions about hetzbot-restore

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

FAQPage Schema
How do I restore a service database and /srv data from a restic snapshot?

To restore a service database and /srv data from a restic snapshot, you need a controlled workflow that coordinates snapshot selection, pre-restore backups, and service restarts to minimize downtime and prevent data loss on the target host.

What is the safest way to perform per-service database recovery on a single host?

Per-service database recovery is safest when using a workflow that includes explicit safety prompts, automatic pre-restore backups, and a controlled sequence of stop, restore, and start with post-restore validation to ensure data integrity.

How does pre-restore backup orchestration work for restic snapshots?

Pre-restore backup orchestration works by creating a safety backup before initiating the restic snapshot recovery, stopping the target service, applying the restore, and then restarting the service with state validation for safe rollback capability.

Can I restore only one specific service instead of rebuilding the entire host?

Yes, you can restore only one specific service instead of a full host rebuild by applying per-service restoration from restic snapshots, which targets the individual service DB and /srv data on a single host.

Do I need host and service mapping to restore data from restic backups?

Yes, you need host and service mapping along with restic integration to restore data from restic backups, because the recovery process requires coordinating snapshot selection and service restarts on the specific target host.

What are the limitations of restoring databases per-service from restic snapshots?

Limitations of restoring databases per-service from restic snapshots include the requirement for a controlled sequence to stop, restore, and start the service, meaning downtime is unavoidable and the process is constrained to per-host services managed by Hetzbot.