Compare commits

...

4 Commits

Author SHA1 Message Date
zenodotus280 7028f4b91d
Merge ea7db2a6b1 into 940a84e21f 2025-06-16 22:39:22 -05:00
Jim Salter 940a84e21f
Merge pull request #1008 from aabccd021/master
Fix readme formatting
2025-06-12 09:53:57 -04:00
aabccd021 680194fa33 Fix readme formatting 2025-06-12 12:58:26 +07:00
zenodotus280 ea7db2a6b1
Add disclaimer if using FreeBSD 14.1
I was able to use initiate `syncoid` successfully from a Debian-based host to a fresh installation of FreeBSD with no configuration changes at all. I hadn't even installed mbuffer or pv - I merely started SSH and was able to replicate right away.

After installing sanoid/syncoid on FreeBSD I found that all the warnings no longer applied: `/usr/local/bin` is the default for all relevant executables and the shebangs were correct.
2024-12-17 18:11:52 -08:00
2 changed files with 2 additions and 0 deletions

View File

@ -166,6 +166,7 @@ Install prerequisite software:
```bash
pkg install p5-Config-Inifiles p5-Capture-Tiny pv mbuffer lzop sanoid
```
_No additional steps are required as of FreeBSD 14.1 - the notes below may apply to versions prior to that._
**Additional notes:**

View File

@ -330,6 +330,7 @@ As of 1.4.18, syncoid also automatically supports and enables resume of interrup
This argument tells syncoid to create a zfs bookmark for the newest snapshot after it got replicated successfully. The bookmark name will be equal to the snapshot name. Only works in combination with the --no-sync-snap option. This can be very useful for irregular replication where the last matching snapshot on the source was already deleted but the bookmark remains so a replication is still possible.
+ --use-hold
This argument tells syncoid to add a hold to the newest snapshot on the source and target after replication succeeds and to remove the hold after the next successful replication. Setting a hold prevents the snapshots from being destroyed. The hold name includes the identifier if set. This allows for separate holds in case of replication to multiple targets.
+ --preserve-recordsize