[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-17。"],[],[],null,["# About volume reversion\n\nThis page provides an overview on snapshot-based volume reversion.\n\nAbout volume reversion\n----------------------\n\nGoogle Cloud NetApp Volumes lets you revert a volume to a previous state using\nthe data captured in a snapshot. Volume reversion restores all the contents of a\nvolume back to the point in time a snapshot was taken. During reversion, any\nsnapshot created after the snapshot you're reverting to is lost. To maintain the\ndata from those snapshots, we recommend that you\n[create a new volume from a snapshot](/netapp/volumes/docs/configure-and-use/volume-snapshots/new-volume-from-snapshot) or [restore specific data with snapshots](/netapp/volumes/docs/configure-and-use/volume-snapshots/restore-specific-data-with-snapshots) instead.\n\nCommon use cases for volume reversion\n-------------------------------------\n\nYou can revert a volume to test and upgrade applications or to fend off\nransomware attacks. Volume reversion is similar to overwriting the volume with a\nbackup, but only takes a few seconds. You can revert a volume to a snapshot\nindependent of the size of the volume.\n\n### Considerations\n\nConsider the following aspects of volume reversion:\n\n- Volume reversion takes a few seconds and happens while the volume is online\n and used by clients.\n\n- Reverting a volume to a prior state deletes any snapshot data taken after the\n snapshot you're using for reversion and the operation is irreversible.\n\n- You can use snapshots to revert a volume to a prior state. You can't revert\n a volume that is in a replication relationship.\n\nRecommendations\n---------------\n\nVolumes with replications should revert to the latest replication snapshot to\nmaintain the replication. Reverting to an older snapshot breaks the replication\nprocess and to start again. To avoid potential data corruption, we recommend\nthat you stop applications using the volume before you perform volume reversion.\n\nWhat's next\n-----------\n\nUse the volume reversion instructions to [revert a volume from a snapshot](/netapp/volumes/docs/configure-and-use/volume-snapshots/revert-volume-instructions)."]]