Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Topik berikut menjelaskan secara singkat penggunaan snapshot dan pencadangan yang diinginkan.
Snapshot
Snapshot adalah resource yang menggunakan kapasitas dalam instance dan memungkinkan Anda mengembalikan status data instance saat ini ke titik waktu tertentu sebelumnya. Pengguna juga dapat memilih untuk kembali ke versi sebelumnya dari file tertentu.
Snapshot tidak mereplikasi data apa pun atau menggunakan kapasitas hingga data di instance diubah. Semua snapshot instance memiliki data yang sama, yang berarti bahwa instance hanya mempertahankan perbedaan antara snapshot.
Meskipun snapshot menawarkan efisiensi biaya jika dibandingkan dengan pencadangan, kapasitas instance yang tersedia terus menurun seiring dengan dilakukannya perubahan file.
Mengembalikan instance ke status sebelumnya bersifat destruktif, karena akan menghapus
data instance versi terbaru, dan harus digunakan dengan hati-hati.
Cadangan
Pencadangan adalah resource eksternal yang berada di luar
instance, yang menggunakan kapasitas terpisahnya sendiri. Pencadangan pertama adalah
salinan lengkap data instance, dengan setiap pencadangan berikutnya hanya menggunakan
data yang diperlukan untuk melacak perubahan inkremental dan diferensial
sejak pencadangan sebelumnya. Secara internal, histori rantai cadangan
dilacak menggunakan snapshot, yang menggunakan kapasitas pada instance
sumber.
Secara default, pencadangan bersifat inkremental untuk menghindari penagihan data redundan dan untuk
meminimalkan penggunaan ruang penyimpanan. Untuk memastikan keandalan histori perubahan
yang mendasarinya, cadangan terkadang dapat mengambil salinan lengkap instance.
Hal ini terjadi secara otomatis untuk memaksimalkan ruang penyimpanan dan meminimalkan biaya penyimpanan.
Anda tidak perlu memilih antara membuat pencadangan inkremental atau lengkap. Saat
cadangan mengambil salinan lengkap instance, snapshot inkremental sebelumnya dari
instance tersebut tidak akan berubah.
[[["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\u003eSnapshots allow reverting an instance's data to a previous state, consuming capacity within the instance and efficiently storing only the differences between snapshots, but they destructively delete the latest version of instance data upon reversion.\u003c/p\u003e\n"],["\u003cp\u003eBackups are external resources that store a complete initial copy of instance data and subsequently track incremental changes, consuming separate capacity and reducing redundancy by default.\u003c/p\u003e\n"],["\u003cp\u003eSnapshots offer a cost-effective approach to preserving data versions compared to backups, though instance capacity continuously decreases as modifications occur.\u003c/p\u003e\n"],["\u003cp\u003eBackups are managed internally using snapshots, allowing them to track the change history of instance data, where periodic full copies of the data are taken to ensure reliability and optimize storage space.\u003c/p\u003e\n"]]],[],null,["# Compare snapshots and backups\n\nThe following topic briefly describes the intended uses of snapshots and backups.\n\nSnapshots\n---------\n\n*[Snapshots](/filestore/docs/snapshots)* are resources that consume capacity\nwithin the instance and allow you to revert the current state of your instance\ndata to a previous, specific point in time. Users can also elect to revert to a\nprevious version of a specific file.\n\nSnapshots don't replicate any data or consume capacity until the data on the\ninstance is modified. All snapshots of an instance share in-common data, meaning\nthat the instance preserves only the differences between the snapshots.\nWhile snapshots do offer cost efficiency when compared to backups, available\ninstance capacity continuously decreases as file modifications are made.\n\nReverting an instance to a previous state is destructive, as it deletes the\nlatest version of instance data, and should be used carefully.\n\nBackups\n-------\n\n*[Backups](/filestore/docs/backups)* are external resources that reside outside\nof the instance, consuming their own separate capacity. The first backup is a\ncomplete copy of instance data, with each subsequent backup only consuming the\ndata necessary to track [incremental and differential](/filestore/docs/backups#backup-creation)\nchanges since the previous backup. Internally, a [backup chain's](/filestore/docs/backups#backup-creation)\nhistory is tracked using snapshots, which consume capacity on the source\ninstance.\n\nBy default, backups are incremental to avoid billing for redundant data and to\nminimize the use of storage space. To ensure the reliability of the underlying\nchange history, a backup may occasionally capture a full copy of the instance.\nThis happens automatically to maximize storage space and minimize storage costs.\nYou don't need to choose between creating incremental or full backups. When a\nbackup captures a full copy of the instance, previous incremental snapshots of\nthat instance are unchanged.\n\nWhat's next\n-----------\n\n- [Learn more about backups](/filestore/docs/backups)\n- [Learn more about snapshots](/filestore/docs/snapshots)"]]
