PVC snapshots¶

Starting with version 1.23.0, you can back up and restore using Kubernetes volume snapshots. A snapshot is a point-in-time copy of a Persistent Volume Claim created through the Volume Snapshot API . Data stays on the storage backend instead of uploading to object storage.

For how snapshots compare to logical and physical backups, and what they do not support, see Backup types. This page lists what you need before you configure them.

If you already know you want snapshots, go to Configure PVC snapshots. On Amazon EKS, start with Set up PVC snapshots on EKS.

Requirements¶

Your Kubernetes cluster must have a CSI driver that supports the VolumeSnapshot API. Examples: pd.csi.storage.gke.io on GKE, ebs.csi.aws.com on EKS.

The VolumeSnapshot CRDs must be installed. Check with:

kubectl get crd | grep volumesnapshot

Expected output

volumesnapshotclasses.snapshot.storage.k8s.iovolumesnapshotcontents.snapshot.storage.k8s.io volumesnapshots.snapshot.storage.k8s.io

At least one VolumeSnapshotClass must exist and match the storage class used by your data volumes:
```
kubectl get volumesnapshotclasses
```
Refer to the Add a VolumeSnapshotClass for the steps.
The cluster Custom Resource must include at least one backup storage entry. PBM stores snapshot metadata there. It does not upload database files for external backups.

Limitations¶

Point-in-time recovery and selective restore are not available for external backups.

Backup and restore flow¶

PBM treats snapshot backups as type external. For what the Operator and PBM do during backup and restore, see How backup and restore work.

Track restore progress in the Restore resource status.conditions field. See PVC snapshot restore conditions.

Restore flow¶

See How backup and restore work for the restore sequence.

Next steps¶

Configure PVC snapshots

Last update: September 2, 2026
Created: September 2, 2026