Search results

@tuonoazzurro This is very strange. Is there no official statement about that?

@tuonoazzurro Are you sure this is something that is happaning in standard environment? Never realized something like that. @DerDanilo Well that's what I though too, until LnxBil "convinced" me... or maybe not convinced.... :confused: This is exactly what I wanted, an discussion about the...

Thanks a lot guys for your help. I really appreciate that.

Well difficult to say because I read a lot of stuff the last days :-). But it was suggested somewhere to not boot from ZFS, and instead do a mdadm raid. So you think that we should not have separate system disks? (using all disks in one ZFS pool that includes system and VMs storage)

@guletz THX for the thoughts. So in later Test Use, how could I determine if a l2arc or slog would improve performance? @LnxBil Hmm.. I read somewhere that for the Linux boot it is better to not use ZFS raid1. So this is why I ended up in using mdadm raid1 for system.

Hi @ all, we are planning actually our new Proxmox Servers and therefore think about the best performing and cost efficient setup. Now we are a bit stuck at using ZIL and L2ARC on separate devices. Here our actual planed setup: Xeon 6134 Gold 254GB ECC DDR4 RAM 2 x 60GB SSD SATA - mdadm Raid...

Any news on that? Is the live migration yet working from the shell on ZFS?

You are writing about vzdump, but I asked about pve-zsync? Is there a way to automate the backup of linked clones with pve-zsync?

Hi @ all, we are facing a similar error on 5.2-3 : The mouse on noVNC also laggs but it is caught by the system cursor. So we only see one cursor that is lagging. Any idea why this problem occours on proxmox 5.2-3, because on 5.2.1 everything is fine?

Hi, thx for the info.

Hi @ all, any news on that? Is someone using this Server successful as node?

Thanks a lot. Now everything is clear.

So that means that the volume "rpool/quaterhourly/vm-122-disk-1" is the last snapshot "rpool/quaterhourly/vm-122-disk-1@rep_vm1-QUATERHOURLY_2018-04-10_11:30:01", and that the volume is always the "most actual copy"? And what does the last snapshot on the working node, that is growing slowly...

Hi@all, I am actually trying to understand pve-zsync but don't get it... I have a working node and a backup node trying to sync snapshots every 15min to the backup node. Here the behaivour of pve-zsync or zfs that I don't understand: on working node Every 2.0s: zfs list -t snapshot -r...

Well unfortunately the new "Replication" feature has still some errors where replication fails! See my post: https://forum.proxmox.com/threads/replication-failed-to-some-node.35684/#post-188445 This is why I am using now pve-zsync instead of replication!

Hi, I did not really got the "gui zfs sync" in your sentence?? Do you mean the "replication" feature? Regards Andreas

@joshin Awsome work!!! The only thing I am missing is the qemu and lxc monitoring. Are you planing to extend it? Regards

@jeanlau I know this post is quite old, but did you managed to create the nagios script? Thx

So is it not planned to implement a "more intelligent" backup feature of linked clones to PVE? So the way I could go withouth having full size backups would be: zfs send -R rpool/data/base-555-disk-1@__base__ | ssh "node-to" zfs recv rpool/data/base-555-disk-1 zfs snapshot...

That sounds "great". I think with ZFS and NVMe SSDs the performance issues should not be a problem, rigth? BTW: Still no info about Backups of linked clones ;-)