Am 15. Mai 2016 20:42:19 MESZ, schrieb Robert Fantini <robertfant...@gmail.com>: >Hello, > >I've got znapzend working on omnios. that can remote send to linux >using a >napp-it job . > >Next I want to run znapzend on linux and pull from omnios . > >this does not work , >znapzendzetup create \ > --tsformat='%Y-%m-%d-%H%M%S' \ > --mbuffer=/usr/bin/mbuffer \ > SRC '7d=>1h,3w=>1d' root@10.2.2.21:data/vm-111-disk-1 \ > DST '7d=>1h,3m=>1d' tank/znapzend/pro4-kvm > >*** backup plan: root@10.2.2.21:data/vm-111-disk-1 *** >dst_0 = tank/znapzend/pro4-kvm >dst_0_plan = 7days=>1hour,3months=>1day >enabled = on >mbuffer = /usr/bin/mbuffer >mbuffer_size = 1G >post_znap_cmd = off >pre_znap_cmd = off >recursive = off >src = root@10.2.2.21:data/vm-111-disk-1 >src_plan = 7days=>1hour,3weeks=>1day >tsformat = %Y-%m-%d-%H%M%S > >Do you want to save this backup set [y/N]? > y >cannot open 'root@10.2.2.21:data/vm-111-disk-1': invalid dataset name >cannot open 'root@10.2.2.21:data/vm-111-disk-1': invalid dataset name >ERROR: could not set property dst_0_plan on root@10.2.2.21: >data/vm-111-disk-1 >
It looks to me that you can only have the DST definition use ssh, not the SRC. From the znapzendzetup documentation at https://github.com/oetiker/znapzend/blob/master/doc/znapzendzetup.pod create [--pfexec|sudo] \ [--recursive] [--mbuffer=<path>[:<port>]] [--mbuffersize=<size>] \ [--pre-snap-command=<command>] \ [--post-snap-command=<command>] \ [--tsformat=<format>] --donotask \ SRC plan dataset \ [ DST[:key] plan [[user@]host:]dataset ] >The SRC zfs exists: >ssh 10.2.2.21 zfs list data/vm-111-disk-1 >NAME USED AVAIL REFER MOUNTPOINT >data/vm-111-disk-1 16.5G 1.17T 16.1G - > > >Any clues on what I am doing wrong? > -- Christian Kivalo _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss