Hetzner Snapshot Backups: A Complete Beginner’s Guide

Introduction

If you host servers on Hetzner, protecting your data should be at the top of your checklist. Snapshots are Hetzner’s built‑in, point‑in‑time backup solution that lets you capture the exact state of a server or volume with a single click. In this guide we’ll walk through what Hetzner snapshot backups are, why they matter, and how to use them effectively – all without pulling your hair out.

What Is a Hetzner Snapshot?

A snapshot is a read‑only image of a server’s disk (or a block storage volume) taken at a specific moment. Unlike traditional backups that copy files to a separate location, Hetzner stores the snapshot in the same data centre, making restores lightning fast. Snapshots are ideal for:

  • Testing software updates before they go live
  • Rolling back after a failed configuration change
  • Creating a baseline before major migrations

How Snapshots Differ From Other Backup Types

Incremental vs. Full

Hetzner snapshots are incremental after the first full capture. Only the blocks that change are stored, which keeps storage costs low. A traditional full backup repeats the entire dataset each time.

Retention and Accessibility

Snapshots remain until you delete them, giving you full control over retention. They are instantly accessible from the Hetzner Cloud console, whereas off‑site backups may require a restore process that can take hours.

Step‑by‑Step: Creating a Snapshot

  1. Log in to the Hetzner Cloud Console. Navigate to the project that contains the server you want to protect.
  2. Select the server. Click the Backups & Snapshots tab.
  3. Click “Create Snapshot”. Give the snapshot a descriptive name (e.g., web‑prod‑2024‑05‑10).
  4. Confirm. Hetzner will queue the snapshot and notify you when it’s ready.

The process usually finishes within a few minutes for standard SSD volumes.

Restoring From a Snapshot

  1. Go to the Backups & Snapshots tab of the target server.
  2. Select the desired snapshot and click Restore.
  3. Choose whether to replace the existing disk or attach the snapshot as a new volume for testing.
  4. Confirm and wait for the restore to complete.

After the restore, your server returns to the exact state captured in the snapshot – applications, configurations, and data alike.

Best Practices for Using Hetzner Snapshots

  • Schedule regular snapshots. Automate creation via Hetzner’s API or a cron job to ensure you always have a recent recovery point.
  • Label clearly. Include dates, environment (prod, staging), and purpose in the snapshot name.
  • Combine with off‑site backups. Snapshots protect against accidental deletion, but not against regional disasters. Export critical snapshots to an external storage service.
  • Test restores quarterly. A backup is only as good as your ability to restore it.
  • Delete old snapshots. Retain only what you need to control costs – a typical rotation is daily for 7 days, weekly for 4 weeks, and monthly for 3 months.

Cost Considerations

Hetzner charges snapshot storage per GB per month. Because snapshots are incremental, the cost is usually a fraction of a full backup. For example, a 100 GB volume with daily snapshots may only use ~30 GB of additional storage after a month.

FAQ

Can I snapshot a running server?

Yes. Hetzner snapshots are taken from a live volume, but it’s recommended to pause high‑I/O services or use a filesystem freeze for mission‑critical data.

Do snapshots affect server performance?

During snapshot creation, Hetzner momentarily locks the volume metadata, which can cause a brief I/O spike. The impact is minimal for most workloads.

Are snapshots encrypted?

Snapshots inherit the encryption status of the original volume. If your server disk is encrypted, the snapshot remains encrypted as well.

How long does a restore take?

Restores typically finish within 5–10 minutes for standard SSD volumes, depending on size.

Can I share a snapshot with another Hetzner project?

Yes. Use the “Share Snapshot” feature in the console or the API to grant access to another project.

Conclusion

Hetzner snapshot backups give you a fast, cost‑effective safety net for any server or volume. By automating snapshot creation, naming them clearly, and complementing them with off‑site backups, you’ll drastically reduce the risk of data loss and downtime.

Ready to secure your Hetzner servers?

Start by creating your first snapshot today, and set up an automated schedule with the Hetzner API. Need help? Contact our support team for a quick setup walkthrough.

Suggested Internal Links

  • "How to Automate Hetzner Backups with the API"
  • "Migrating Servers Between Hetzner Data Centres"

External Reference

For deeper technical details, see Hetzner’s official documentation on snapshots (Hetzner Cloud Docs).

Comments are closed, but trackbacks and pingbacks are open.