| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| automated_zfs_snapshots_for_omv5 [2021/05/06 00:42] – crashtest | automated_zfs_snapshots_for_omv5 [2021/05/06 00:48] – [Pool Snapshots] crashtest |
|---|
| \\ | \\ |
| **For ZFS users:**\\ | **For ZFS users:**\\ |
| This guide will show how to setup and take advantage of one of ZFS' most valuable features for restoration, SNAPSHOTS. **zfs-auto-snapshot**, automatically creates, prunes, and purges periodic snapshots. Other than ZFS utilities, which are installed with the ZFS filesystem and cron, which is part of most Linux installations, there are no specific dependencies. | This guide will show how to setup and take advantage of one of ZFS' most valuable features for restoration, SNAPSHOTS.\\ |
| | **zfs-auto-snapshot**, automatically creates, prunes, and purges periodic snapshots. Other than ZFS utilities, which are installed with the ZFS filesystem and cron, which is part of most Linux installations, there are no specific dependencies. |
| |
| While intended primarily for openmendiavault, this How-To and the package zfs-auto-snapshot will work with other Linux distributions with ZFS on Linux (ZOL). | While intended primarily for openmendiavault, this How-To and the package zfs-auto-snapshot will work with other Linux distributions with ZFS on Linux (ZOL). |
| \\ | \\ |
| **In the interests of clarity:**\\ | **In the interests of clarity:**\\ |
| A ZFS “filesystem” is interchangeable with a standard Linux folder at the root of the pool and is navigable, on the command line, in the same manner. The difference is a standard Linux folder at the root of the pool, is part of the parent pool. A child “filesystem” is created by ZFS and is assigned editable ZFS properties. A “filesystem snapshot” is taken independent of the parent pool and is independently restoreable. \\ | A ZFS “filesystem” is interchangeable with a standard Linux folder at the root of the parent pool and is navigable, on the command line, in the same manner. The difference is a standard Linux folder at the root of the pool, is part of the parent pool. A child “filesystem” is created by ZFS and is assigned editable ZFS properties. A “filesystem snapshot” is taken independent of the parent pool and is independently restoreable. \\ |
| \\ | \\ |
| ---- | ---- |
| \\ | \\ |
| zfs set com.sun:auto-snapshot=**true** Rocky\\ | zfs set com.sun:auto-snapshot=**true** Rocky\\ |
| | \\ |
| zfs set com.sun:auto-snapshot:frequent=true Rocky\\ | zfs set com.sun:auto-snapshot:frequent=true Rocky\\ |
| zfs set com.sun:auto-snapshot:hourly=true Rocky\\ | zfs set com.sun:auto-snapshot:hourly=true Rocky\\ |