[SOLVED] snapshots ZFS?

Really strange, the snapshots must be exists on both hosts. What say "pve-zsync list" on the host you added the job?
 
Thanks for the reply, on host 1 I get this

Code:
root@prometheus:~# pve-zsync list
SOURCE                   NAME                     STATE     LAST SYNC           TYPE  CON
123                      test2                    ok        2018-03-23_21:21:01 qemu  ssh
 
Ok, you have an existing working pve-zsyncjob, you have snapshots on first host, an no Datasets on second host, but an working pve-zsyncjob, sorry for the question, but do you really have the right second host?
 
Thanks for the reply
not sure what do you mean?
sorry for the question, but do you really have the right second host?

um well in theory the snapshots should be on the host 2 rather then on the host 1? or am i doing this all wrong lol.
 
On both hosts have to be the same datesets (synct with pve-zsync) and on both hosts have to be the same snapshots. This it how it works. For example here my homesync:

Code:
@weekly root pve-zsync sync --source v-machines/home --dest [2001:470:1e1b:589:ec4:7bfe:fabb:c725]:v-machines --name home --maxsnap 8 --method ssh

First host (created job)
Code:
zfs list -t snapshot

v-machines/home@rep_home_2018-01-28_00:00:01                                5.51G      -  3.53T  -
v-machines/home@rep_home_2018-02-04_00:00:02                                70.8M      -  3.53T  -
v-machines/home@rep_home_2018-02-11_00:00:01                                66.4M      -  3.53T  -
v-machines/home@rep_home_2018-02-18_00:00:01                                69.9M      -  3.53T  -
v-machines/home@rep_home_2018-03-04_00:00:01                                 603M      -  3.54T  -
v-machines/home@rep_home_2018-03-11_00:00:01                                 799M      -  3.54T  -
v-machines/home@rep_home_2018-03-18_00:00:02                                1.77G      -  3.54T  -
v-machines/home@rep_home_2018-03-25_00:00:01                                18.1M      -  3.54T  -

Secondhost Target:
Code:
zfs list -t snapshot

v-machines/home@rep_home_2018-01-28_00:00:01                                5.52G      -  3.53T  -
v-machines/home@rep_home_2018-02-04_00:00:02                                86.8M      -  3.53T  -
v-machines/home@rep_home_2018-02-11_00:00:01                                81.0M      -  3.53T  -
v-machines/home@rep_home_2018-02-18_00:00:01                                85.5M      -  3.53T  -
v-machines/home@rep_home_2018-03-04_00:00:01                                 622M      -  3.53T  -
v-machines/home@rep_home_2018-03-11_00:00:01                                 811M      -  3.54T  -
v-machines/home@rep_home_2018-03-18_00:00:02                                1.78G      -  3.54T  -
v-machines/home@rep_home_2018-03-25_00:00:01                                   0B      -  3.53T  -
 
Thanks for the reply,
Code:
 pve-zsync sync --source v-machines/home --dest [2001:470:1e1b:589:ec4:7bfe:fabb:c725]:v-machines --name home --maxsnap 8 --method ssh
So the only difference i had from this would be the IP which mine is IPV4, the part of v-machines is that where you also host your vms? on the 2nd host and 1st host?
I think i messed up complete using this guide https://www.servethehome.com/automating-proxmox-backups-with-pve-zsync/

The worst part i cant seem to remove on the 2nd host the vmdata/vmbackup data sheet it keeps saying

Code:
zfs destroy -R vmdata/vmbackup
      cannot destroy 'vmdata/vmbackup': dataset already exists

so in theory this is what i should do both host 1 and host 2 have the same rpool and vmdata pool
so to backup the vms from host 1 to host 2 it would be like this

Code:
pve-zsync create --source 123 --dest 192.168.3.80:vmdata --verbose --maxsnap 7 --name test3
Meaning creating from scratch the job backing up vm 123 to host 2 which is going to vmdata?

Thank you
 
So the only difference i had from this would be the IP which mine is IPV4, the part of v-machines is that where you also host your vms? on the 2nd host and 1st host?
IPV4 and 6, that makes no difference. V-Machines is my Source and on the other machine also the targetpool. No there are no VM's there. The VM's are on an dataset. I sync no VM's, only the datasets from host1, so here HOME.

Meaning creating from scratch the job backing up vm 123 to host 2 which is going to vmdata?
No, look at the documentation, you need an dataset too.
 
do i need to have the same data sheet from host 1? as on host 1 i do not have data sheet /vmbackup
 
do i need to have the same data sheet from host 1? as on host 1 i do not have data sheet /vmbackup
No, but it make it much more easier. For example. if i sync VMXXX from host1 to host 2 then i have on host1 and host2 the dateset v-machines/HDD-vmdata-KVM. The advantage is that after moved the configfile to /etc/pve/qemu-server, i'am immediately able to start the VM, without change the config hddpath to special dataset like backup or vmbackup....
 
Thanks for the reply, but i thought the idea is to have the snapshots on the other host 2 rather then on host 1?
 
o wow i did not know that howcome? i think that might be the issue as host 1 does not have the same data sheet as host1 might need the vmbackup sheet
 
I wanted to Thank @fireon that he helped me personally, He found that the issue was that i created a zol running this command
Code:
zfs create -s -V 400g

The correct command is
Code:
zfs create vmdata/vmbackup
then give it a quota

Code:
zfs set quota=400g vmdata/vmbackup

also the previous vmdata/vmbackup had childs which he helped me to delete which was the reason it wont not delete
 
  • Like
Reactions: fireon

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!