Closed killmasta93 closed 3 years ago
Two things:
[data]
instead of [/data]
. I'm not sure if that could be the cause of your problem, but something I noticed.data
and 64 hourly on data2
. That will lead to a mismatch since all frequent snapshots on data2
will be deleted and then you don't have any common snapshots.Apart from that everything looks ok and should work as you expected it to. Try to fix those two things and see if it works then. You could also try to send without a config, i.e. do pyznap send -s data -d data2
and see if that works.
Thank you so much for the reply, that did the trick remove the / I will also change the 64 frequent thanks for pointing that out, Out of curiosity, is it possible to run dry run and possible to show the ETA?
Great, glad that solved it. A dry run is not possible currently, so there is no way to show an ETA before actually starting the zfs send. Duration also depends on quite a lot of things (speed of both drives, internet connection if send over ssh, ...).
HI, I was wondering if someone could shed some light on the issue im having. Currently i have ZFS pool called data and i need to migrate to another pool called data2 within the same machine
this is the pool i have
and the config
i first ran pyznap snap
then ran pyzsnap send
but i get this, it seems that its not sending the info to data2
Thank you