Snapshot volume Kubernetes memungkinkan Anda membuat salinan volume pada titik waktu
tertentu. Anda dapat menggunakan salinan ini untuk mengembalikan volume ke status sebelumnya atau untuk menyediakan volume baru.
Anda dapat menggunakan snapshot untuk melindungi workload dan mencapai tujuan titik pemulihan bisnis yang penting dalam rencana pemulihan dari bencana, atau jika Anda memiliki keperluan terkait kepatuhan untuk menyimpan data secara berkala.
GKE mendukung dua cara untuk membuat snapshot volume:
API snapshot volume antarmuka penyimpanan container (CSI): Ini adalah proses manual yang memungkinkan Anda membuat dan mengelola snapshot volume melalui driver CSI Persistent Disk Compute Engine atau driver CSI Filestore, dengan menerapkan konvensi konfigurasi yang umum digunakan dalam pemrograman Kubernetes open source.
Pencadangan untuk GKE: Ini adalah layanan terkelola sepenuhnya yang mengotomatiskan pembuatan dan pengelolaan snapshot volume. Pencadangan untuk GKE
mendukung pencadangan konfigurasi dan volume
untuk workload stateful dengan persistent disk. Untuk beban kerja dengan Filestore, hanya pencadangan konfigurasi yang didukung. Untuk mencadangkan data di instance tingkatan dasar Filestore, Anda harus terus menggunakan API snapshot volume melalui driver CSI Filestore.
Mulai GKE versi 1.17 atau yang lebih baru, Anda dapat menyediakan dan memasang
snapshot volume dengan komponen berikut:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-14 UTC."],[],[],null,["# About volume snapshots\n\n[Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) [Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nIn Google Kubernetes Engine (GKE), you can use the Kubernetes\n[volume snapshot feature](https://kubernetes.io/docs/concepts/storage/volume-snapshots/)\nfor [persistent volumes](/kubernetes-engine/docs/concepts/persistent-volumes)\nin your GKE clusters.\n\n- Kubernetes volume snapshots let you create a copy of your volume at a specific\n point in time. You can use this copy to bring a volume back to a prior state or\n to provision a new volume.\n\n- A [volume snapshot in Kubernetes](https://kubernetes.io/docs/concepts/storage/volume-snapshots/) is equivalent to taking a backup of your data in other\n storage systems. For example, creating a Kubernetes volume snapshot is\n equivalent to creating a [Filestore backup](/filestore/docs/backups).\n\n- You can use snapshots to protect your workloads and achieve business-critical\n recovery point objectives in your disaster recovery plan, or if you have\n compliance needs to periodically save data.\n\nGKE supports two ways to create volume snapshots:\n\n- **Container storage interface (CSI) volume snapshot API** : This is a manual\n process that lets you create and manage volume snapshots through the\n [Compute Engine Persistent Disk CSI driver](/kubernetes-engine/docs/how-to/persistent-volumes/gce-pd-csi-driver)\n or the [Filestore CSI driver](/kubernetes-engine/docs/how-to/persistent-volumes/filestore-csi-driver),\n applying configuration conventions commonly used in open source Kubernetes\n programming.\n\n- **Backup for GKE** : This is a fully-managed service that automates the creation\n and management of volume snapshots. [Backup for GKE](/kubernetes-engine/docs/add-on/backup-for-gke/concepts/backup-for-gke)\n supports both the [configuration and volume backup](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/backup)\n for stateful workloads with persistent disks. For workloads with Filestore,\n only the configuration backup is supported. To back up data in your\n Filestore [basic tier](/filestore/docs/service-tiers) instances, you\n should continue to use the volume snapshot API through the Filestore\n CSI driver.\n\nFrom GKE version 1.17 or later, you can provision and attach\nvolume snapshots with the following components:\n\n- [VolumeSnapshotClass](https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes/)\n\n- [VolumeSnapshot](https://kubernetes.io/docs/concepts/storage/volume-snapshots/)\n\n- [VolumeSnapshotContent](https://kubernetes.io/docs/concepts/storage/volume-snapshots/#volume-snapshot-contents)\n\n| **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`.\n\nThe following documentation covers how to use the volume snapshot API with a\nGKE CSI driver:\n\n- [Back up and restore Filestore storage using volume snapshots](/kubernetes-engine/docs/how-to/persistent-volumes/backup-filestore-volume-snapshots).\n\n- [Back up and restore Persistent Disk storage using volume snapshots](/kubernetes-engine/docs/how-to/persistent-volumes/backup-pd-volume-snapshots).\n\nWhat's next\n-----------\n\n- Read the [Kubernetes Volume Snapshot](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-cis-volume-snapshot-beta/) documentation.\n- Learn about [volume expansion](/kubernetes-engine/docs/how-to/volume-expansion).\n- Learn how to [manually install a CSI driver](/kubernetes-engine/docs/how-to/install-csi-driver).\n- Learn about [Filestore support for GKE](/filestore/docs/filestore-for-gke)."]]
