yboetz
commented
5 years ago About your config: There is no send = yes keyword. If you specify a (or multiple) dest, then pyznap will try to send to them. And you should always specify full paths, so e.g. dest_keys = /home/user/.ssh/id_rsa. This should not give you the errors you see though, as the send keyword is just ignored and the ssh connection seemed to have worked anyway. The rest of the config seems ok. You should see the snapshots after running pyznap snap using
zfs list -r zones -t snapNow for your send problem, it seems that pyznap does not find the necessary executables for lzop, mbuffer and pv. It should check if these are available though, so it is strange that it tries to use them in the first place. Are lzop, mbuffer and pv installed on both your source and dest? Can you post the output of
which lzop
which mbuffer
which pv
lzop --versionI never used SmartOs (or Solaris) and haven't tested pyznap on it. But this seems like some of the paths are different than on linux and thus pyznap is confused. You might also have to change the PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin line in the crontab. Please also post the output of
echo $PATH
shotelco
Set up pyznap on a SmartOS (Solaris-like) host. Looks like everything is correct except for the send functionality. I want to backup a local SAMBA/CIFS share mounted as a ZFS volume to a remote SAMBA/CIFS share. Doing a full backup, then incremental backups managed by pyznap. I configured a simple pyznap.conf. When forcing a snap, there seems to be no errors, when forcing a send, there are numerous errors. I likely do not understand how actually doing a volume backup works with pyznap. Any help would be appreciated:
backup test1
[zones/0f..trunkated..ec/data/petashare1/admin] hourly = 1 snap = yes send = yes clean = yes dest = ssh:22:root@192.168.3.105:zones/90..trunkated..76/data/home/backupblob dest_keys = .ssh/id_rsa
compress = gzip
snap output: [root@SMB1 /opt/local/bin]# ./pyznap snap Sep 04 20:58:41 INFO: Starting pyznap... Sep 04 20:58:41 INFO: Taking snapshots... Sep 04 20:58:41 INFO: Taking snapshot zones/0f..trunkated..ec/data@pyznap_2019-09-04_20:58:41_hourly... Sep 04 20:58:41 INFO: Cleaning snapshots... Sep 04 20:58:41 INFO: Deleting snapshot zones/0f..trunkated..ec/data@pyznap_2019-09-04_19:59:46_hourly... Sep 04 20:58:41 INFO: Deleting snapshot zones/0f..trunkated..ec/data/petashare1@pyznap_2019-09-04_19:59:46_hourly... Sep 04 20:58:42 INFO: Deleting snapshot zones/0f..trunkated..ec/data/petashare1/admin@pyznap_2019-09-04_19:59:46_hourly... Sep 04 20:58:42 INFO: Deleting snapshot zones/0f..trunkated..ec/data/petashare1/backupblob@pyznap_2019-09-04_19:59:46_hourly... Sep 04 20:58:42 INFO: Finished successfully...
No errors, even though I can't find the snapshots.
send output:
[root@SMB1 /opt/local/bin]# ./pyznap send Sep 04 21:05:54 INFO: Starting pyznap... Sep 04 21:05:54 INFO: Sending snapshots... Sep 04 21:05:57 INFO: No common snapshots on root@192.168.3.105:zones/90..trunkated..76/data/home/backupblob, sending oldest snapshot zones/0f..trunkated..ec/data@pyznap_2019-09-04_20:58:41_hourly (~12.6K)... sh[1]: lzop: not found [No such file or directory] Sep 04 21:05:59 ERROR: Error while sending to root@192.168.3.105:zones/90..trunkated..76/data/home/backupblob: bash: lzop: command not found - cannot receive: failed to read from stream... Sep 04 21:06:00 INFO: No common snapshots on root@192.168.3.105:zones/90..trunkated..76/data/home/backupblob/petashare1, sending oldest snapshot zones/0f..trunkated..ec/data/petashare1@pyznap_2019-09-04_20:58:41_hourly (~13.6K)... sh[1]: lzop: not found [No such file or directory] Sep 04 21:06:00 ERROR: Error while sending to root@192.168.3.105:zones/90..trunkated..76/data/home/backupblob/petashare1: bash: lzop: command not found - cannot receive: failed to read from stream... Sep 04 21:06:01 INFO: No common snapshots on root@192.168.3.105:zones/90..trunkated..76/data/home/backupblob/petashare1/admin, sending oldest snapshot zones/0f..trunkated..ec/data/petashare1/admin@pyznap_2019-09-04_20:58:41_hourly (~8.5M)... sh[1]: lzop: not found [No such file or directory] sh: line 1: mbuffer: not found sh: line 1: pv: not found Sep 04 21:06:04 ERROR: Error while sending to root@192.168.3.105:zones/90..trunkated..76/data/home/backupblob/petashare1/admin: bash: lzop: command not found - cannot receive: failed to read from stream... Sep 04 21:06:04 INFO: No common snapshots on root@192.168.3.105:zones/90..trunkated..76/data/home/backupblob/petashare1/backupblob, sending oldest snapshot zones/0f..trunkated..ec/data/petashare1/backupblob@pyznap_2019-09-04_20:58:41_hourly (~12.6K)... sh[1]: lzop: not found [No such file or directory] Sep 04 21:06:05 ERROR: Error while sending to root@192.168.3.105:zones/90..trunkated..76/data/home/backupblob/petashare1/backupblob: bash: lzop: command not found - cannot receive: failed to read from stream... Sep 04 21:06:05 INFO: Finished successfully...
Although I was not using the cron in crontabs, for your reference, here it is: cron/crontab/pyznap: SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
!# /15 root /opt/local/bin/pyznap snap >> /var/log/pyznap.log 2>&1 !# /20 root /opt/local/bin/pyznap send >> /var/log/pyznap.log 2>&1
This may be a pyznap.conf error? Thanks in advance.