Skip to content

AutoSnap

Automated snapshot scheduling and management for Proxmox VE virtual machines.

Features

  • Scheduled Snapshots

    Create snapshots automatically based on cron schedule with retention policies.

  • Retention Policies

    Define how many snapshots to keep per VM, with automatic cleanup of expired ones.

  • Job Management

    Configure snapshot jobs with cron schedule, VM selection, execution history and status monitoring.

  • Multi-VM Support

    Apply a single job to multiple VMs and containers using filters or explicit selection.

  • Node-independent

    Jobs target VM IDs, ranges, name wildcards, pools or tags (with optional exclusions) — unless you use @node-…, they are not tied to a node. When a VM migrates (manual or HA failover), the next scheduled snapshot just runs on its new home with no reconfiguration.

  • Web API Hook

    Trigger HTTP webhooks on snapshot phase events (before/after create, before/after delete). Configure per-job HTTP endpoints with custom headers and body templates.

    Learn more

Why

Proxmox can already take snapshots — why use a module for it?

Snapshots actually happen

On a schedule you choose. No human has to remember before the next risky operation.

Manage 50 VMs as one set

A single job targets a group via tags, wildcards or explicit list — no copy-paste per VM.

Different schedules per workload

Hourly for the database, nightly for dev VMs, weekly for templates — each job runs on its own cron, side by side on the same cluster.

Follows the VM, not the node

Jobs target VM IDs / pools / tags, not a node (unless you use @node-…). When a VM migrates to another node, the next snapshot just runs there — no reconfiguration needed.

Retention without thinking

Set Keep=7 once; the module deletes the 8th snapshot for you. Plain Proxmox keeps them forever until someone notices.

Storage-safe by default

MaxPercentageStorage skips the snapshot when the target pool is too full — your storage never fills because of automation.

Auditable history

Every run logged in the Jobs grid, Time line and Errors tab — you know what was snapshotted, when, and what failed.

Sections

  • Jobs — manage AutoSnap jobs: target VMs, schedule, label, retention, include RAM, only while running, max parallel, optional Web API Hook . Per job, Snap takes the snapshots immediately and Purge Snapshots deletes all the snapshots with the job's label on its VMs
  • Time line — visual timeline of snapshots created across jobs and VMs
  • Errors — history of failed snapshot operations with the underlying error message
  • Status — inventory of AutoSnap snapshots, grouped by label and VM with counts and size; selected snapshots can be deleted

Settings

Show all settings
Setting Default Purpose
Enabled off Master on/off switch for the cluster
Keep History 10 Maximum number of past run results to keep per job
Notify None When to send notifier events: never, on errors, always
Search Mode Managed How snapshots created by AutoSnap are identified (Managed = recognised by name pattern only)
Timestamp Format engine default Format applied to the {timestamp} placeholder in snapshot names
On Remove Job Remove Snapshots on Delete the snapshots created by a job when the job itself is deleted
Max Percentage Storage 95 Skip snapshot creation if the target storage is more full than this percentage — prevents filling the pool
Notifier Configurations – List of Notifier configurations to deliver events to