ZFS: Difference between revisions
imported>Grahamc Show an example pool layout which keeps /nix out of the hierarchy of /, and create a list of explicitly recommended dataset properties. |
imported>Grahamc Don't be so certain that no user will want to snapshot the Nix store. |
||
| Line 164: | Line 164: | ||
ZFS can take consistent and atomic snapshots recursively down a | ZFS can take consistent and atomic snapshots recursively down a | ||
dataset's hierarchy. Since Nix is good at being Nix, | dataset's hierarchy. Since Nix is good at being Nix, most users will want their server's ''data'' backed up, and don't | ||
mind reinstalling NixOS and then restoring data. If this is sufficient, only snapshot and back up the <code>safe</code> hierarchy. Users who want to be able to restore a service with only ZFS snapshots will want to snapshot the entire tree, at the significant expense of snapshotting the Nix store. | |||
=== Dataset Properties === | === Dataset Properties === | ||