I am attempting to create a new backup set while using the "--rootExec=sudo" argument, as I do not want to root SSH to the remote system to invoke "zfs receive" command. However, when I create it the backup set, the following errors occur:
sudo: no tty present and no askpass program specifiedWARNING: executable '/usr/bin/mbuffer' does not exist on ... (though it does)*** WARNING: destination 'user@10.100.10.21:pool1/fs1/fs2/fs3' does not exist, will be ignored! ***, though it does
Lastly, when I run znapzend --noaction --debug, it just hangs.
Thoughts?
I have some strace output but its probably too verbose to post here, but here are the last few lines (it goes into a sleep cycle):
nanosleep({tv_sec=1, tv_nsec=0}, 0x7fff277d7a40) = 0
nanosleep({tv_sec=0, tv_nsec=0}, NULL) = 0
nanosleep({tv_sec=1, tv_nsec=0}, 0x7fff277d7a40) = 0
nanosleep({tv_sec=0, tv_nsec=0}, NULL) = 0
Can't be 100% sure but I believe the issue lies with a ZoL bug #8478. With ZFS version 0.7.5 shipping with Ubuntu 18.0.4, I think its only possible to send zfs send/receive streams with root user.
What are the recommended steps to synchronize two data sets if I want to pre-seed the remote site with a backup of the local site sent/received to a pool on an external disk array, then sent/received a second time to the remote site while attached locally over USB? Pool dataset size is around 30TB.
Note: I cannot do an initial sync across the wire due to ISP related issues.
I am having issues installing Znapzend on a variant of Xenial Ubuntu. Here is the output below:
root@D52T-1ULH-1:/tmp/znapzend-0.19.0# /usr/bin/make install
Making install in thirdparty
make[1]: Entering directory '/tmp/znapzend-0.19.0/thirdparty'
GEN touch
Successfully installed Mojolicious-6.46
Successfully installed Module-Build-0.4224
Successfully installed IO-Pipely-0.005
Successfully installed Mojo-IOLoop-ForkCall-0.17
! Installing Scalar::Util failed. See /tmp/znapzend-0.19.0/thirdparty/work/1564546113.26736/build.log for details. Retry with --force to force install it.
Successfully installed Test-Harness-3.42 (upgraded from 3.35)
5 distributions installed
Makefile:408: recipe for target 'touch' failed
make[1]: *** [touch] Error 123
make[1]: Leaving directory '/tmp/znapzend-0.19.0/thirdparty'
Makefile:495: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1
Yes, that was the issue, thank you. The default mirrors on the box would not allow the build tools to be installed, so I compiled on another system.
My next issue is as follows. I did a distribution upgrade on a different system where znapzend has been running for over a year. I deleted and then re-added back nearly the same plan (with some slight changes; I cannot use the edit command because 'vi' doesnt work properly on my Mac's Bash shell for some reason). I attempted to invoke the runonce command, and got the following error back:
cannot receive new filesystem stream: destination has snapshots (eg. pool1/fs1/fs2/fs3)
must destroy them to overwrite it
mbuffer: error: outputThread: error writing to <stdout> at offset 0x80000: Broken pipe
mbuffer: warning: error during output to <stdout>: Broken pipe
My question is, how is it possible for the snapshots to get out of sync simply by way of adding/deleting a new plan? Does this mean I have to once resync everything? If that is the case, that would be the second time in less than 6 months. With over 20TB of data, that is not a sustainable solution and then might have to look at alternatives.
There most certainly be snapshots in common between the two systems, but how do I get znapzend to recognize that?
Any suggestions would be helpful.
So I've upgraded my Proxmox box to 6 (debian 10) and now I'm getting a problem when trying to execute Znapzend. I really know nothing about Perl so would appreciate any assistance...
root@cat:~# znapzend list
ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xce00080)
