> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.ibee.co.in/docs/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ibee.co.in/docs/_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 → \ → 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** | Workspace-wide catalog of recovery points and point-in-time copies across your VMs, with a **Take Snapshot** button. | The Tools page is the aggregate view. A search box filters by snapshot, VM, volume, or ID, and the list is paginated. Each row shows: | Column | Description | | ------------ | ------------------------------------------------------------------------------------------------------------------ | | **Snapshot** | Snapshot name and a short identifier (with a copy button). | | **Disks** | What was captured (for example `Root volume · 1 disk`). | | **Storage** | Snapshot footprint. | | **Status** | `Available` once the snapshot is ready; in-progress states such as `Creating` or `Pending` while it's being taken. | | **Created** | Date and time. | | **Action** | Row menu with **Manage snapshot**, which opens the snapshot's details. | **Manage snapshot** shows the snapshot's name, type (recovery point or volume snapshot), snapshot ID, source VM, source volume, disks, capture mode, storage, status, created/updated times, and description — plus **Delete Snapshot**. Restores are started from the VM's **Snapshots** tab. **Take Snapshot** on the Tools page opens a dialog with: * **Virtual Machine** — pick a VM. * **Snapshot Name** — required. * **Description** — optional note for this restore point. * **Capture Mode** — **Root volume only**, **All attached volumes**, or **Selective volumes** (tick the data volumes to include). If the VM has no attached data volumes, the snapshot is root-only. * A reminder to run `sync` inside the VM to flush pending writes before taking the snapshot. Both surfaces offer the same capture modes. Use the per-VM **Snapshots** tab when you also want to browse recovery points and restore. ## 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)