Thalassa Cloud Thalassa Cloud
Sign in Sign up

Volume Snapshots & Snapshot Policies

Point-in-time, incremental snapshots for block volumes with automated snapshot policies. Fast restores and Kubernetes CSI integration.

Sign up for a free account

Volume Snapshots for Data Protection

Volume snapshots provide point-in-time, incremental copies of block volumes without disrupting running workloads. Use snapshots for backups, disaster recovery, and environment cloning.

Point-in-Time Recovery

Capture exact volume state at any moment without disrupting running workloads. Restore volumes to any previous snapshot state instantly for database rollbacks, environment cloning, and disaster recovery.

  • Instant snapshot creation without service interruption
  • Fast restore to any previous snapshot state
  • Database rollback and recovery capabilities
  • Environment cloning for testing and development

Incremental Storage

Only changed blocks are stored, making snapshots space-efficient and cost-effective. Reduce storage costs while maintaining comprehensive backup coverage.

  • Incremental snapshots store only changed blocks
  • Significant storage cost savings
  • Maintain comprehensive backup coverage
  • Efficient snapshot chains and deduplication

Automated Snapshot Policies

Define automated snapshot schedules with cron-style formatting and flexible retention policies. Target specific volumes or groups of volumes via labels. Combine short-term and long-term retention strategies.

  • Cron-based scheduling for automated snapshots
  • Flexible retention policies (hourly, daily, weekly)
  • Label-based volume targeting
  • Combine multiple retention strategies

Kubernetes CSI Integration

Manage snapshots using Kubernetes-native VolumeSnapshot and VolumeSnapshotClass resources. Integrate with backup tools like Velero for comprehensive data protection strategies.

  • Native Kubernetes VolumeSnapshot API support
  • VolumeSnapshotClass for snapshot configuration
  • Integration with Velero and other backup tools
  • Restores always create new volumes (source unchanged)

Automated Snapshot Policies

Define automated snapshot schedules with cron-style formatting and flexible retention policies. Target specific volumes or groups of volumes via labels.

Cron Scheduling Flexible Retention Label Targeting

Kubernetes CSI Integration

Manage snapshots using Kubernetes-native VolumeSnapshot and VolumeSnapshotClass resources. Integrate with backup tools like Velero for comprehensive data protection strategies.

VolumeSnapshot API Velero Integration Kubernetes Native

Get Started with Volume Snapshots

Automate your data protection with snapshot policies, fast restores, and seamless Kubernetes integration.

Sign up for a free account Contact Us

Snapshot Policy Example

# Create snapshot policy
apiVersion: v1
kind: SnapshotPolicy
metadata:
  name: daily-backup
spec:
  schedule: "0 2 * * *"  # Daily at 2 AM
  retention:
    days: 30
    keepCount: 7
  target:
    labels:
      app: database
      env: production

Frequently Asked Questions

Volume snapshots are point-in-time copies of block volumes. They capture the exact state of a volume at a specific moment without disrupting running workloads:

  • Snapshots are created instantly without service interruption
  • Snapshots can be restored to create new volumes
  • Original volumes remain unchanged during snapshot creation

This makes snapshots ideal for backups, disaster recovery, and environment cloning.

Thalassa Cloud snapshots integrate seamlessly with Kubernetes using the Container Storage Interface (CSI) snapshot API:

  • Use VolumeSnapshot and VolumeSnapshotClass Kubernetes resources
  • Create snapshots of PersistentVolumeClaims directly from Kubernetes
  • Restore snapshots to create new PersistentVolumeClaims

This provides a native Kubernetes experience for snapshot management without requiring external tools or manual volume operations.

Snapshot policies automate the creation and management of volume snapshots:

  • Scheduling: Use cron-style schedules to define when snapshots are created (e.g., daily at 2 AM)
  • Retention: Configure how long snapshots are kept (e.g., 30 days, keep last 7 snapshots)
  • Targeting: Use labels to target specific volumes or groups of volumes
  • Multiple Strategies: Combine short-term (hourly) and long-term (weekly) retention strategies

Policies automatically create snapshots according to the schedule and manage retention, reducing manual effort and ensuring consistent backup coverage.

Snapshots use incremental storage, meaning only changed blocks are stored:

  • First snapshot stores all data blocks
  • Subsequent snapshots store only blocks that have changed
  • Storage usage depends on how much data changes between snapshots
  • Typically much more space-efficient than full volume copies

This makes snapshots cost-effective for maintaining comprehensive backup coverage while minimizing storage costs. You only pay for the storage actually used by changed blocks.

Yes, restoring from a snapshot always creates a new volume, keeping the original source unchanged:

  • Restore creates a new volume from the snapshot
  • Original volume remains intact and unchanged
  • Restored volume can be attached to different instances or used in different environments
  • Perfect for testing, development, or disaster recovery scenarios

This safe restore behavior ensures you can experiment with restored volumes without risk to your original data.

European Public Cloud

DevOps-First Cloud

Deploy and manage your cloud-native applications with our European based public cloud. Access powerful APIs, Kubernetes orchestration, and DevOps tools designed for modern infrastructure.

GDPR Compliant

EU Data Sovereignty

API First

Terraform & REST API

Kubernetes

Self-Service Kubernetes as a Service

High Performance

NVMe Storage, CPU and network

Launch Your Cloud Journey

Code. Ship. Scale. • Pay-as-you-go pricing