Skip to main content

Overview

A snapshot captures the state of a volume at a specific point in time. Snapshots are and stored within the same storage cluster as the source volume. Creating a snapshot takes seconds — only metadata is recorded at creation time, with changed blocks tracked incrementally. Snapshots are ideal for pre-change checkpoints, test environment cloning, and fast volume recovery.
Prerequisites
  • An active project with snapshot quota available (openstack quota show)
  • The source volume must exist (it can be attached or detached)
  • For application-consistent snapshots of databases, quiesce writes or use a maintenance window before creating the snapshot

Snapshot vs Backup

FeatureSnapshotBackup
Storage locationSame cluster as source volumeSeparate backup target
Creation timeSeconds (metadata + COW tracking)Minutes (full data copy)
Incremental supportImplicit (copy-on-write)Yes — after first full backup
Survives cluster failureNoYes
Restore timeSeconds (new volume from snapshot)Minutes (data restore)
Use caseFast recovery points, cloningLong-term retention, disaster recovery
Use snapshots for frequent, short-term checkpoints. Use backups for long-term retention and disaster recovery scenarios.

Create a Snapshot

Navigate to Volumes

Log in to the Xloud Dashboard (https://connect.<your-domain>) and navigate to Project → Volumes → Volumes.

Create snapshot

Locate the target volume and click Actions → Create Snapshot.Provide a descriptive name and optional description, then click Create Volume Snapshot.
Name snapshots with a timestamp and purpose for easy identification — e.g., db-primary-2026-03-18-pre-migration.

Verify

Navigate to Project → Volumes → Snapshots. The new snapshot appears with status Available.
Snapshot created — status shows Available.

Restore from a Snapshot

Restoring creates a new independent volume pre-populated with the snapshot data. The original source volume and snapshot are unaffected.

Navigate to Snapshots

Navigate to Project → Volumes → Snapshots.

Create volume from snapshot

Click Actions → Create Volume on the desired snapshot. Configure the new volume name, type, and availability zone, then click Create Volume.
The new volume size defaults to the snapshot size. You can specify a larger size, but not smaller.

Attach the restored volume

The restored volume appears in the Volumes list with status Available. Attach it to an instance and verify the data.
Volume restored from snapshot and ready for attachment.

Delete a Snapshot

Snapshot deletion is permanent and cannot be undone. Ensure no volumes are currently being created from the snapshot before deleting it. Volumes that depend on a snapshot (created from it) must be deleted first if the backend requires it.
Navigate to Project → Volumes → Snapshots. Click Actions → Delete Snapshot on the target snapshot and confirm the deletion.

Troubleshooting

Cause: The storage backend did not complete the snapshot operation within the expected timeout, or the volume is in an inconsistent state.Resolution:
Check snapshot status
openstack volume snapshot show <snapshot-id> -c status
Wait a few minutes for backends under load. If the snapshot remains in creating for more than 10 minutes, contact your administrator — the backend may require manual cleanup.
Cause: The backend encountered an error during snapshot creation. Common causes include insufficient storage capacity or backend driver issues.Resolution:
Delete the failed snapshot
openstack volume snapshot delete <snapshot-id>
Check available capacity on the storage cluster and retry. Do not repeatedly retry on a degraded backend — resolve the underlying storage issue first.
Cause: A volume was created from this snapshot and the backend tracks the dependency. Some backends require the child volume to be deleted before the snapshot.Resolution: Delete the volumes created from the snapshot first, then delete the snapshot.

Application-Consistent and File-Level Restore

For application-consistent snapshots with XAVS Guest Agent coordination (filesystem freeze, VSS provider for Windows, custom hooks) and agentless file-level restore, see the Compute snapshots guide. The file-level restore feature lets you browse and download individual files from any snapshot.

Instance Snapshots and Backups

Application-consistent snapshots, XAVS Guest Agent integration, and agentless file-level restore from the Dashboard

Next Steps

Volume Backups

Create full and incremental backups for long-term retention and disaster recovery

Extend a Volume

Increase volume capacity before or after restoring from a snapshot

Attach / Detach

Attach a restored volume to a compute instance

Create a Volume

Create a new volume from an image, snapshot, or blank