Time Machine Backups - Revision history

188.136.90.201: Tested Time machine on ZFS raidz1/cache successfully.

2023-10-13T12:06:27Z

Tested Time machine on ZFS raidz1/cache successfully.

2023-10-13T12:05:22Z

‎zvols

2023-10-08T16:53:25Z

Does not work under Ventura

2023-10-08T16:52:41Z

‎Sparsebundles

2021-08-10T23:43:09Z

‎zvols

2020-01-15T17:52:22Z

Add the option to backup via network shares set up with the com.apple.devdisk and com.apple.mimic_hfs properties.

2020-01-01T02:06:36Z

Added info about network backups

2018-10-19T05:35:05Z

‎zvols

2018-09-19T06:38:21Z

2018-09-18T01:15:29Z

‎Time Machine Backups

← Older revision		Revision as of 12:06, 13 October 2023
Line 25:		Line 25:

	Tested successfully under Ventura using raidz1 with cache disk (all disks on USB).		Tested successfully under Ventura using raidz1 with cache disk (all disks on USB).
		+

	<li>Create a zvol to use for Time Machine backups:		<li>Create a zvol to use for Time Machine backups:

@@ Line 24: / Line 24: @@
 <ol>
-Does not work under Ventura.
+Tested successfully under Ventura using raidz1 with cache disk (all disks on USB).
 <li>Create a zvol to use for Time Machine backups:

← Older revision		Revision as of 16:53, 8 October 2023
Line 23:		Line 23:

	<ol>		<ol>
		+
		+	Does not work under Ventura.

	<li>Create a zvol to use for Time Machine backups:		<li>Create a zvol to use for Time Machine backups:

@@ Line 17: / Line 17: @@
 The hypothesis being that an HFS+ sparsebundle stored on a compressed (gzip, lz4), deduped dataset should
 yield a compression ratio > 1.0 (previously observed 1.4 with compression=on, dedup=off, FreeBSD network Time Machine drives).
 === zvols ===

@@ Line 78: / Line 78: @@
 Time Machine can backup over the network to either HFS+ or APFS target volumes, shared via SMB.  If you try to do this with a ZFS target volume, the client gets an error saying "The selected network backup disk does not support the required capabilities."
-So the trick is to create an HFS+ or APFS target volume on your zpool.  There are two ways to do that, explained in the section above about local backups: create the volume as a sparse bundle, or as a zvol.
+You have two options from this point on:
 You don't need the steps that set the volume as a time machine destination on the server; it's just going to be shared over the network.  When you share the volume on the network, follow the instructions at https://support.apple.com/guide/mac-help/a-shared-folder-time-machine-mac-mchl31533145/mac to make it available as a TimeMachine volume.

@@ Line 1: / Line 1: @@
-== Time Machine Backups ==
+== Backup to Local Disk ==
 There are two approaches to using ZFS for Time Machine Backups - Sparsebundles on a ZFS data set and zvols formatted as HFS+.
@@ Line 73: / Line 73: @@
 <code>diskutil cs list | grep -e "Conversion" -e "Volume Name"</code>

← Older revision		Revision as of 05:35, 19 October 2018
Line 70:		Line 70:
	<code>sudo diskutil coreStorage convert disk5s2 -passphrase</code>		<code>sudo diskutil coreStorage convert disk5s2 -passphrase</code>

−	Please note, this process can take a considerable amount of time (several hours for a 1TB volume).	+	Please note, this process can take a considerable amount of time (several hours for a 1TB volume). You can check on the progress of the encryption using the following command:
		+
		+	<code>diskutil cs list \| grep -e "Conversion" -e "Volume Name"</code>

@@ Line 30: / Line 30: @@
 . Get OSX disk number corresponding to the zvol:
-<code>ioreg -trn "ZVOL [pool]/[volume]" | awk -F'"' '/BSD Name/ {print $4;}'</code>
+<code>ioreg -trn "ZVOL [pool]/[volume] Media" | awk -F'"' '/BSD Name/ {print $4;}'</code>
 For example, if a zvol named tmdisk1 was created as shown above, the following will get its disk number and store it in the shell variable DISKID:
-<code>ioreg -trn 'ZVOL Backup/tmdisk1' | awk -F'"' '/BSD Name/ {print $4;}'</code>
+<code>ioreg -trn 'ZVOL Backup/tmdisk1 Media' | awk -F'"' '/BSD Name/ {print $4;}'</code>
 . Format the zvol as a HFS+, using its disk number from step 2: