Search results

Thanks a lot, i always wondered what mechanism is sending this #zfsrocks - virtualization with Proxmox and ZFS that backups itself! is showing how we are snapshotting and in the next episode how we replicate zfs-data the cronjobs creating mails that we are analyzing with sharepoint foundation...

sorry, idead serial driver was missing. installed it and working fine so if service not starting, install missing serial driver. think this is a newer feature

same here on windows 10. service does not start, proxmox checked for agent. any idea?

okay, i will do. thanks is there a reference how the mails are triggered? do i have to reboot after the upgrade?

Hi, since 5.1(fresh install) my houry, daily etc cronjobs do not longer end in an email how can i restore this behaviour? chriz

now its working! thanks a lot

i am just upgrading the 5.0 to 5.1, was a fresh installation, but i missed the stick on the second system. so i did not verify. and btw. zfs is usually compatible for years back

F***** I took a 5.0 Stick to install on Target side!!!!!!!!! I´ll try 5.1

yes, i tested an old upgraded zfs on target and created a new one with pve 5.1

yes i am a zfs youtube podcaster and have tested as described above! zfs send -pv rpool2/data/HIS-KASSEN@zfs-auto-snap_hourly-2017-10-31-1617 | ssh root@10.0.0.9 zfs recv -dvF Raid10 after transmiting the snapshot it takes forever and only can be interupted by ctrl+c and remote side crashing

That is the output.after finishing the first snapshot replication, both getting stucked The sending site can be stopped without effect The receiving side hast to be rebooted

I have fresh install and none ssh replication is running, neighter manual nor by gui

Same pveversion on both sides? I am not the only one with those problems

https://bugzilla.proxmox.com/show_bug.cgi?id=1550

https://bugzilla.proxmox.com/show_bug.cgi?id=1550

same here today https://forum.proxmox.com/threads/pve-5-1-does-not-not-finish-zfs-replication.37820/#post-186369 stop replication tasks an reboot machines if possible to stop it

so i tested it with a cluster. fresh install on both machines with PVE Storage Replication via Web GUI replication takes forever for 64kb dataset () Replication Log 2017-11-01 18:29:00 101-0: start replication job 2017-11-01 18:29:00 101-0: guest => VM 101, running => 0 2017-11-01 18:29:00...

pve-zsync is based on ssh zfs send, so I don’t think it’s working on 5.1 Aonyone uses that combo on 5.1?

It only does one snapshot at a time So if a manual transfer does not work, an automatic should have problems as well

hi, fresh installation does not complete any ssh replication. first tested on pve 3.4 as a targen, then I updated and used a fresh created zpool as a target after first replication the system does not finish the job canceling the replication is working and freezes the target to busy the dataset...