automated_zfs_snapshots_for_omv5

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
Last revisionBoth sides next revision
automated_zfs_snapshots_for_omv5 [2021/05/06 00:43] – [Automated ZFS Snapshots] crashtestautomated_zfs_snapshots_for_omv5 [2022/07/26 01:35] – crashtest
Line 1: Line 1:
-<html><center><strong>Automated ZFS Snapshots for openmediavault 5</strong></center></html>+<html><center><strong>Automated ZFS Snapshots for Openmediavault 5 and 6</strong></center></html>
  
 {{ :zfs1.jpg?400 |}} {{ :zfs1.jpg?400 |}}
  
-====== Automated ZFS Snapshots for openmediavault 5 ======+====== Automated ZFS Snapshots for Openmediavault 5 and 6 ======
 \\ \\
 <html><center><strong>How To setup automated, Self  Rotating and Purging ZFS snapshots</strong></center></html> <html><center><strong>How To setup automated, Self  Rotating and Purging ZFS snapshots</strong></center></html>
Line 82: Line 82:
 \\ \\
 **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. \\
 \\ \\
 ---- ----
Line 95: Line 95:
 \\ \\
 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\\
Line 144: Line 145:
 While rolling back a file system or the parent pool is relatively easy, if going significantly back in time (beyond the most recent snapshot) the roll back feature will not work in the OMV GUI.  However, a roll back can be done with the following command line: While rolling back a file system or the parent pool is relatively easy, if going significantly back in time (beyond the most recent snapshot) the roll back feature will not work in the OMV GUI.  However, a roll back can be done with the following command line:
  
-(In this example, the roll back would be done to the entire parent pool “Rocky”.)+(In this example, the roll back would be done to the parent pool “Rocky”.)
  
 ''zfs rollback Rocky@zfs-auto-snap_hourly-2018-01-14-1617 -r''    ''zfs rollback Rocky@zfs-auto-snap_hourly-2018-01-14-1617 -r''