Recent content by IsThisThingOn

muss es ja auch nicht (wenn Quelle und Ziel ZFS sind und ZFS selbst bit rot erkennt) ;)

I am not 100% sure on that one. Sure, I have pretty low backup requirements (around 20 Linux VMs and 8 Windows VMs, 182 snapshots at 1.5TB) but I only see 800MBit/s and 500 IOPS peak. So I am not entirely convinced it would be much slower with HDDs instead of my SSD mirror. Yes, it is writing...

But it is :) A Hardware RAID5 with 4 drives will give you exactly 75% storage efficiency. A ZFS RAIDZ1 with 4 drives will give you between 50% and 75%, depending on padding and pool geometry. Which in return depends on your zvol and dataset settings and what file you plan on saving onto it...

Sure. VEEAM supports PVE, so PVE backups are supported by VEEAM. PBS supports PVE, so PVE backups to PVS are supported by Proxmox. Support means that someone will pick up the phone or give you the option to write a ticket. As a rule of thumb, the more these companies depend on support...

True, but at the same time, why would I want Support from Proxmox for my backup tool? IMHO it does not matter, what PVE supports. If I use VEEM for my proxmox backup, the only thing that matters is IMHO that VEEAM supports backing up a PVE host. Just like Windows does not officially support...

Not sure, but is it maybe just the missing ' ? That could also be the case. I created the user on pbs, so that is why I am using that. I also just gave it full admin rights and deleted the user afterwards.

Depends. Rsync should be pretty good at batching metadata over slow networks. AFAIK the bottlneck should be the storage metadata performance. PBS on the other hand reads ALL you lokal data, and creates a hash. So you lokal storage and CPU performance could be a bottleneck. ZFS send would...

Yeah, my redacted IPv6 Jup, not a problem. Proxmox GUI just displays the pools, no matter how they are created. But you probably could also create it in the webGUI.

proxmox-backup-client benchmark --repository mybackupstore For me, that was something like this: proxmox-backup-client benchmark --repository 'test@pbs@[2001:XXXXXXXXXXXX::f691]:8007:poolBackup' Correct, I suggest you create multiple mirrors inside the same vdev. So basically a stripe over all...

Then the TLS speed should be your bottleneck, since the PBS storage is too slow to write above 200MB/s. That is pretty bad for 2-4MB chunks IMHO. But to be expected with a 6 wide RAIDZ2. You could switch to mirrors, that way you should be able to get 500MB/s, at which point other bottlenecks...

Run the benchmark on PVE with PBS as destination. Then run the benchmark again on PBS. Post both results

First of all, what are we talking about? What do you mean by "migrating"? Is it the backup from PVE to PBS speed you are unhappy with?

I thought I might share this with you guys. Could be interesting. I personally never really understood why dedup has to be "live". But to be honest, I don't know much about dedup. https://github.com/openzfs/zfs/commit/afb4010325a52413c0ad813885eed50738a8380b

IMHO it is more like me having a sailing boat and a 5PS small motor. There might be wind, and I might be able to travel at 20km/h. But I don't count on it. I know that worst case, there is no wind and I have to use my 5PS motor which will get me 4km/h. BTW this is a very real example. You can...

Interesting. IMHO the underlying issue is to rely on ARC for performance. IMHO ARC should only be looked at as a "boost" or "(free) performance gain" and not as a given. Not only because it is a little bit unpredictable, but also because it has to become hot and is lost after a reboot.