> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ibee.ai/docs/tools/snapshots/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ibee.ai/_mcp/server.

# VM snapshots

> Capture on-demand recovery points for IBEE Solutions VMs and restore in place or into a new VM.

A **snapshot** is an on-demand recovery point captured from a running Cloud VM. Each snapshot includes the root disk and, optionally, attached data volumes. Snapshots are kept as a **Recovery Point** that you can restore in place, use to create a new VM, or roll back disk-by-disk.

Snapshots and [automated backups](/docs/tools/backups) share the same restore flow. Use snapshots when you want a recovery point at a specific moment — before a deploy, OS upgrade, or risky migration. Use backups for continuous, schedule-driven protection.

## What's captured

Every snapshot captures the **root disk** by default. You choose how much else to include via **Capture Mode**:

| Capture Mode             | Captures                                                    |
| ------------------------ | ----------------------------------------------------------- |
| **Root volume only**     | Just the boot disk. Attached data volumes are skipped.      |
| **All attached volumes** | Root disk plus every attached persistent data volume.       |
| **Selective volumes**    | Root is always included; pick specific data volumes to add. |

Restoring a snapshot set automatically reattaches captured data volumes to the target VM. Mount instructions for each data volume are surfaced in the Details drawer.

## Restore options

When you click **Restore** on a snapshot recovery point, the same three modes are offered as backup restore:

| Mode                      | Effect                                                                        |
| ------------------------- | ----------------------------------------------------------------------------- |
| **Replace Current VM**    | Roll back the existing VM's root disk and captured data disks in place.       |
| **Create New VM**         | Provision a brand-new VM from the recovery point with new live block volumes. |
| **Restore Selected Disk** | Roll back a single captured disk on the current VM.                           |

See [Restore a snapshot](/docs/tools/snapshots/restore-a-snapshot) for full steps.

## When to take a snapshot

* Before a **deploy** or migration you might need to roll back.
* Before an **OS upgrade** or kernel change.
* To **clone a known-good build** into a new VM via the **Create New VM** restore mode.
* As a **manual checkpoint** between scheduled backup runs.

For routine, ongoing protection, prefer scheduled [automated backups](/docs/tools/backups).

## Where to manage snapshots

Two surfaces in the IBEE Solutions portal manage snapshots:

| Surface                               | Use it for                                                                                                                                                                          |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Cloud VMs → \<VM> → Snapshots tab** | Rich per-VM flow: pick a Capture Mode (Root only / All attached / Selective), browse Recovery Points, and restore in three modes (Replace · Create New VM · Restore Selected Disk). |
| **Tools → Snapshots**                 | Organization-wide catalog of block volume snapshots — point-in-time copies of your block volumes, with running totals (for example **1 · 50 GB total**).                            |

The organization-level page is the aggregate view. It lists every snapshot with:

| Column            | Description                                                 |
| ----------------- | ----------------------------------------------------------- |
| **Snapshot**      | Name and short identifier you set when taking the snapshot. |
| **Source Volume** | Volume UUID the snapshot was taken from.                    |
| **Size**          | Snapshot footprint (for example `50 GB`).                   |
| **Status**        | `Available` once the snapshot is ready to restore.          |
| **Created**       | Date and time.                                              |
| **Action**        | Per-row menu (delete, copy ID, …).                          |

A **Take Snapshot** button on the Tools page opens a simpler dialog:

* **Virtual Machine** — pick a VM (running VMs are marked, e.g. `test · 2 vCPU · 8 GB RAM · 50 GB disk · running`).
* **Snapshot Name** — required label.
* **Description** — optional.
* A reminder: **For data consistency, run `sync` inside the server to flush pending writes before taking the snapshot.**

Use the organization-level dialog for ad-hoc, single-volume snapshots. Use the per-VM **Snapshots** tab when you need Capture Mode or guided restore options.

## Quick start

1. Open the VM detail page → **Snapshots** tab.
2. Enter a **Label** (required) and an optional **Description**.
3. Pick a **Capture Mode** — Root only, All attached, or Selective.
4. (Selective only) Tick the data volumes to include.
5. Click **Create Snapshot**. The recovery point appears in the **Recovery Points** list when complete.

See [Create a snapshot](/docs/tools/snapshots/create-a-snapshot) for the full flow.

## Recovery point list

Each row shows:

* **Snapshot** — your label and the system-generated identifier (for example `srp-20260509T162709Z`).
* **Disks** — what's captured (`Root + 1 data disk`, `2 disk(s)`, …).
* **Created** — date and time.
* **Storage** — total recovery footprint.
* **Actions** — **Details**, **Restore**, **Delete**.

## Snapshots vs. backups

|               | Snapshots                                        | Backups                                |
| ------------- | ------------------------------------------------ | -------------------------------------- |
| Cadence       | On demand                                        | Daily or Weekly schedule               |
| Trigger       | Manual click                                     | Automatic                              |
| Capture mode  | Root only · All attached · Selective             | All attached (root + all data volumes) |
| Restore modes | Replace · Create New VM · Restore Selected Disk  | Same                                   |
| Best for      | Pre-deploy checkpoints, ad-hoc rollback, cloning | Continuous protection, DR              |

Most production VMs use both: scheduled backups as the safety net, manual snapshots before risky changes.

## Related pages

* [Create a snapshot](/docs/tools/snapshots/create-a-snapshot)
* [Restore a snapshot](/docs/tools/snapshots/restore-a-snapshot)
* [Cross-region snapshots](/docs/tools/snapshots/cross-region-snapshots)
* [VM backups](/docs/tools/backups)

> Capture on-demand recovery points for IBEE Solutions VMs and restore in place or into a new VM.

## Docs

- [Create a snapshot](https://docs.ibee.ai/docs/tools/snapshots/create-a-snapshot.md): Capture a manual recovery point of a Cloud VM — root disk plus optional data volumes.
- [Restore a snapshot](https://docs.ibee.ai/docs/tools/snapshots/restore-a-snapshot.md): Roll back a Cloud VM, create a new VM, or restore a single disk from a snapshot recovery point.
- [Cross-region snapshots](https://docs.ibee.ai/docs/tools/snapshots/cross-region-snapshots.md): Copy snapshots across IBEE regions for disaster recovery and cross-region cloning.