Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    yes, that's what I eventually ended up doing as well. not perfect, but acceptable Commented Mar 10, 2021 at 16:56
  • 1
    per the github.com/jimsalterjrs/sanoid/issues/… the -r switch is needed to sync also the datasets of the pool and the command will only work/transfer the data if the destination pool, dataset doe snot yet exist on destination. Same command can be used repeatedly and it should keep the pool2 datasets in sync with pool1. Also it supported resume in my case. So i could do Ctrl+C and then run it again to resume sync. Commented Apr 24, 2021 at 12:16
  • 2
    Another switched worth considering: --skip-parent --no-stream It may not sync parent(pool, but only datasets, which may get rid of a syncoid warning). --no-stream is important for keeping only most recent syncoid snapshot, saving the disk space. Commented Nov 3, 2022 at 17:50