In Google Kubernetes Engine (GKE), you can use the Kubernetes
[volume snapshot feature](https://kubernetes.io/docs/concepts/storage/volume-snapshots/)
for [persistent volumes](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes.md.txt)
in your GKE clusters.

- Kubernetes volume snapshots let you create a copy of your volume at a specific
  point in time. You can use this copy to bring a volume back to a prior state or
  to provision a new volume.

- A [volume snapshot in Kubernetes](https://kubernetes.io/docs/concepts/storage/volume-snapshots/) is equivalent to taking a backup of your data in other
  storage systems. For example, creating a Kubernetes volume snapshot is
  equivalent to creating a [Filestore backup](https://docs.cloud.google.com/filestore/docs/backups.md.txt).

- You can use snapshots to protect your workloads and achieve business-critical
  recovery point objectives in your disaster recovery plan, or if you have
  compliance needs to periodically save data.

GKE supports two ways to create volume snapshots:

- **Container storage interface (CSI) volume snapshot API** : This is a manual
  process that lets you create and manage volume snapshots through the
  [Compute Engine Persistent Disk CSI driver](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/gce-pd-csi-driver.md.txt)
  or the [Filestore CSI driver](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/filestore-csi-driver.md.txt),
  applying configuration conventions commonly used in open source Kubernetes
  programming.

- **Backup for GKE** : This is a fully-managed service that automates the creation
  and management of volume snapshots. [Backup for GKE](https://docs.cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/concepts/backup-for-gke.md.txt)
  supports both the [configuration and volume backup](https://docs.cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/how-to/backup.md.txt)
  for stateful workloads with persistent disks. For workloads with Filestore,
  only the configuration backup is supported. To back up data in your
  Filestore [basic tier](https://docs.cloud.google.com/filestore/docs/service-tiers.md.txt) instances, you
  should continue to use the volume snapshot API through the Filestore
  CSI driver.

From GKE version 1.17 or later, you can provision and attach
volume snapshots with the following components:

- [VolumeSnapshotClass](https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes/)

- [VolumeSnapshot](https://kubernetes.io/docs/concepts/storage/volume-snapshots/)

- [VolumeSnapshotContent](https://kubernetes.io/docs/concepts/storage/volume-snapshots/#volume-snapshot-contents)

> [!NOTE]
> **Note:** In Kubernetes version 1.20, the VolumeSnapshot API version was [promoted to GA](https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/). In GKE 1.23, `snapshot.storage.k8s.io/v1beta1` is deprecated. If you are using a GKE cluster version 1.21 and later, migrate to `snapshot.storage.k8s.io/v1`.

The following documentation covers how to use the volume snapshot API with a
GKE CSI driver:

- [Back up and restore Filestore storage using volume snapshots](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/backup-filestore-volume-snapshots.md.txt).

- [Back up and restore Persistent Disk storage using volume snapshots](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/backup-pd-volume-snapshots.md.txt).

## What's next

- Read the [Kubernetes Volume Snapshot](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/) documentation.
- Learn about [volume expansion](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/volume-expansion).
- Learn how to [manually install a CSI driver](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/install-csi-driver).
- Learn about [Filestore support for GKE](https://docs.cloud.google.com/filestore/docs/filestore-for-gke.md.txt).