[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-09-04(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)"]]
