Skip to Content
Open Beta — managed Kubernetes, DNS & more are live.
📸

Snapshots and backups

Updated 2026-11-20
On this page

Snapshots and backups

Snapshots capture the state of an instance so you can restore or clone it later. Schedule automatic snapshots to protect your workloads without manual effort.

A snapshot is a point-in-time image of an instance. You can launch a new instance from it or rebuild the original, which makes snapshots the fastest way to roll back a bad change or to clone a known-good server.

Beyond one-off snapshots, you can set an automated schedule that captures an instance on a recurring basis and keeps a chosen number of copies (retention). Before you turn a schedule on, Patrii Cloud estimates how much storage it will use so there are no surprises. You can also protect an important snapshot so it cannot be deleted by accident.

Screenshot — The Snapshots tab on an instance, listing captured snapshots and a Snapshot schedule button
The Snapshots tab on an instance, listing captured snapshots and a Snapshot schedule button

Key concepts

Snapshot — A point-in-time image of an instance you can restore or clone from.

Backup — A snapshot managed on a retention cycle for recovery.

Snapshot schedule — A recurring rule that captures an instance automatically.

Retention — How many scheduled copies are kept before the oldest is removed.

Protection — A flag that blocks deletion of a snapshot until you turn it off.

Before you start

  • An instance to capture.
  • Enough image/snapshot storage quota for the copies you keep.
  • For a schedule, a frequency and retention that fit your recovery needs.

Step by step

  1. Open the instance

    Open the instance and go to its Snapshots tab.

    Screenshot — The instance's Snapshots tab
    The instance's Snapshots tab
  2. Take a snapshot

    Choose Create snapshot, give it a name, and confirm; it appears in the list once captured.

    Screenshot — The Create snapshot dialog with a name field
    The Create snapshot dialog with a name field
  3. Set up a schedule
    • Open Snapshot schedule.
    • Set a frequency and a retention count.
    • Review the storage estimate before saving.
    Screenshot — The snapshot schedule form showing frequency, retention and the storage estimate
    The snapshot schedule form showing frequency, retention and the storage estimate
  4. Protect important snapshots

    Turn on protection for a snapshot you must not lose so it cannot be deleted by accident.

  5. Restore or clone

    Rebuild the instance from a snapshot, or launch a brand-new instance from it.

Examples

Take a snapshot with the CLI
patrii server snapshot create web-1 \
  --name web-1-before-upgrade

# daily snapshot at 02:00 UTC, kept 7 days
patrii server snapshot-schedule set <server-id> \
  --frequency daily --hour 2 --retention 7
Launch a new instance from a snapshot
patrii server create \
  --name web-1-clone \
  --image web-1-before-upgrade \
  --flavor <flavor> \
  --network private-net \
  --key my-key
Take a snapshot with Terraform
resource "patrii_instance_snapshot" "before_upgrade" {
  instance_id = patrii_instance.web.id
  name        = "web-1-before-upgrade"
}

Limits & specifications

Snapshot and backup actions:

ActionWhat it does
Create snapshotCapture the instance right now.
Snapshot scheduleCapture automatically on a recurring basis.
Storage estimatePreview the storage a schedule will use.
ProtectBlock deletion of a snapshot.
Restore / RebuildReturn an instance to a snapshot's state.
DeleteRemove a snapshot you no longer need.

Best practices

  • Take a snapshot before risky changes such as upgrades so you can roll back quickly.
  • Schedule snapshots for anything you cannot easily recreate, and set a retention that matches your recovery window.
  • Protect the snapshots you rely on so they survive cleanups.
  • Test a restore occasionally so you know your snapshots actually recover.
  • Remember snapshots use storage; prune old ones and watch the estimate.

FAQ

What's the difference between a snapshot and a backup?
Both capture an instance; a backup is managed on a retention cycle so older copies are pruned automatically. Use scheduled snapshots with retention for ongoing protection and a one-off snapshot before a specific change.
How much storage will a schedule use?
Open Snapshot schedule and review the storage estimate before saving; it accounts for your frequency and retention.
How do I roll back after a bad change?
Rebuild the instance from the snapshot taken before the change, or launch a new instance from it and switch over.
Why can't I delete a snapshot?
It is likely protected. Turn off protection first, then delete it.

Learn more

Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.

Was this article helpful?
Thank you for your feedback. Still stuck? Contact us