Mengembalikan berbagi file ke status ringkasan sebelumnya
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Panduan berikut menunjukkan cara mengembalikan
instance, khususnya satu berbagi file dalam instance, ke status
snapshot sebelumnya.
Haruskah Anda menggunakan operasi revert?
Fitur snapshot kembali adalah operasi yang tidak dapat diurungkan, baik untuk sistem file
aktif maupun untuk snapshot yang lebih baru dalam rantai. Gunakan fitur kembalikan dengan hati-hati.
Untuk penjelasan yang lebih mendetail, lihat Kembali ke status snapshot.
Semua data yang ditulis setelah pembuatan snapshot target akan dihapus
di awal proses pengembalian dan tidak dapat dipulihkan. Semua snapshot
yang lebih baru dari snapshot target juga akan dihapus. Misalnya,
snapshot1, snapshot2, dan snapshot3 dibuat secara berurutan. Mengembalikan
instance ke status yang diambil di snapshot2 berarti semua data yang ditulis
setelah snapshot2, serta semua snapshot yang diambil setelah pembuatan
snapshot2, akan dihapus dalam proses pengembalian.
Meskipun operasi pembatalan dapat memerlukan waktu hingga dua menit untuk diselesaikan, pembersihan data yang dihapus dapat memerlukan waktu antara enam jam hingga sepuluh hari, bergantung pada jumlah file yang terlibat. Anda harus menunggu operasi pembatalan selesai sebelum
memulai operasi pembatalan lainnya.
INSTANCE_ID dengan nama instance tempat Anda ingin
menerapkan operasi revert. Misalnya, my-instance-1.
SNAPSHOT_ID dengan nama snapshot yang ingin Anda gunakan untuk
operasi revert. Misalnya, my-snapshot-3.
LOCATION dengan lokasi instance. Contoh, us-central1.
Anda harus menunggu operasi pembatalan selesai sebelum dapat memulai
operasi pembatalan lainnya untuk instance. Operasi pembatalan dapat memerlukan waktu hingga
dua menit. Namun, proses pembersihan data dan reklamasi ruang dapat memerlukan waktu antara enam jam hingga sepuluh hari. Selama proses ini, ruang yang dipulihkan
akan tersedia secara bertahap saat operasi pembersihan selesai
dan semua ruang yang dipulihkan akan tersedia. Untuk mengetahui informasi selengkapnya, lihat
Batasan snapshot.
[[["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-08-18 UTC."],[[["\u003cp\u003eThis guide explains how to revert a single file share within a Filestore instance to a previous snapshot state, using the \u003ccode\u003erevert\u003c/code\u003e operation.\u003c/p\u003e\n"],["\u003cp\u003eReverting to a snapshot is irreversible, deleting all data written after the target snapshot and any newer snapshots, so users should use this feature cautiously.\u003c/p\u003e\n"],["\u003cp\u003eThe revert process can take up to two minutes, but cleanup of deleted data can take between six hours and ten days, and only one revert operation can run on an instance at a time.\u003c/p\u003e\n"],["\u003cp\u003eOnly instances with a single file share can utilize the revert snapshot feature, and it is incompatible with Filestore multishares for GKE.\u003c/p\u003e\n"],["\u003cp\u003eTo revert a file share, users must unmount the share from clients and then use the \u003ccode\u003egcloud filestore instances revert\u003c/code\u003e command with the instance ID, target snapshot ID, and instance location.\u003c/p\u003e\n"]]],[],null,["# Revert a file share to a prior snapshot state\n\nThe following guide shows you how to [revert](/filestore/docs/reference/rest/v1/projects.locations.instances/revert)\nan instance, specifically a single file share within an instance, to a prior\nsnapshot state.\n\nShould you use the `revert` operation?\n--------------------------------------\n\nThe revert snapshot feature is an irreversible operation, both to the live file\nsystem and to the newer snapshots in the chain. Use the revert feature carefully.\nFor a more detailed explanation, see [Revert to a snapshot state](/filestore/docs/snapshots#revert-to-snapshot).\n\nAll data written after the creation of the target snapshot is deleted\nat the beginning of the revert process and cannot be recovered. All snapshots\nthat are newer than the target snapshot are also deleted. For example,\n`snapshot1`, `snapshot2`, and `snapshot3` are created sequentially. Reverting\nthe instance to the state captured in `snapshot2` means that all data written\nafter `snapshot2`, as well as all snapshots taken after the creation of\n`snapshot2`, are deleted in the revert process.\n\nWhile a revert operation can take up to two minutes to complete, cleanup of the\ndeleted data can take between six hours to ten days, depending on the number\nof files involved. You must wait for the revert operation to complete before\nstarting another revert operation.\n\nOnly instances with a single share can revert to a snapshot state. The revert\nsnapshot feature can't be combined with [Filestore multishares for GKE](/filestore/docs/multishares).\nFor more information, see [Snapshot feature limitations](/filestore/docs/snapshots#feature_limitations)\nor the [`gcloud filestore instances revert`](/sdk/gcloud/reference/filestore/instances/revert)\npage.\n\nUse gcloud CLI to revert a file share to a previous snapshot\n------------------------------------------------------------\n\n### gcloud CLI\n\nTo revert a file share to the state captured in a snapshot:\n\n1. Unmount the file share from clients:\n\n sudo umount \u003cvar translate=\"no\"\u003emount-point-directory\u003c/var\u003e\n\n2. Revert the file share to a snapshot state using the [`instances revert`](/sdk/gcloud/reference/filestore/instances/revert)\n command:\n\n gcloud filestore instances revert \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e \\\n --target-snapshot=\u003cvar translate=\"no\"\u003eSNAPSHOT_ID\u003c/var\u003e \\\n --location=\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e with the name of the instance where you want to apply the `revert` operation. For example, `my-instance-1`.\n - \u003cvar translate=\"no\"\u003eSNAPSHOT_ID\u003c/var\u003e with the name of the snapshot you want to use for the `revert` operation. For example, `my-snapshot-3`.\n - \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e with the location of the instance. For example, `us-central1`.\n\nYou must wait for the revert operation to complete before you can start\nanother revert operation for the instance. Revert operations can take up to\ntwo minutes. However, the data cleanup and space reclamation process can take\nbetween six hours to ten days to complete. During this process, the reclaimed\nspace becomes available gradually while the cleanup operation finishes\nand all reclaimed space is available. For more information, see\n[Snapshot limitations](/filestore/docs/snapshots#feature-limitations).\n\nWhat's next\n-----------\n\n- [Snapshots overview](/filestore/docs/snapshots)\n- [Restore a file from a snapshot](/filestore/docs/restore-file)\n- [Schedule Filestore enterprise snapshots](/filestore/docs/schedule-filestore-enterprise-snapshots)\n- [Backups overview](/filestore/docs/backups)"]]
