zfs storage pool checkpoint
The idea of Storage Pool Checkpoint (aka zpool checkpoint) deals with exactly that. It can be thought of as a “pool-wide snapshot” (or a variation of extreme rewind that doesn’t corrupt your data).
It remembers the entire state of the pool at the point that it was taken and the user can revert back to it later or discard it. Its generic use case is an administrator that is about to perform a set of
destructive actions to ZFS as part of a critical procedure. She takes a checkpoint of the pool before performing the actions, then rewinds back to it if one of them fails or puts the pool into an
unexpected state. Otherwise, she discards it. With the assumption that no one else is making modifications to ZFS, she basically wraps all these actions into a “high-level transaction”.
Updated by Electric Monk almost 2 years ago
- % Done changed from 0 to 100
- Status changed from New to Closed
commit 8671400134a11c848244896ca51a7db4d0f69da4 Author: Serapheim Dimitropoulos <email@example.com> Date: 2018-03-14T16:49:34.000Z 9166 zfs storage pool checkpoint Reviewed by: Matthew Ahrens <firstname.lastname@example.org> Reviewed by: John Kennedy <email@example.com> Reviewed by: Dan Kimmel <firstname.lastname@example.org> Approved by: Richard Lowe <email@example.com>