Warum willst du überhaupt pushen? Für Backups gegen s3 ist das natürlich nötig, bei PBS muss dagegen der pushende PBS auf den anderen schreiben können, was der pull-sync vermeidet. Wenn du also nicht gerade unverschlüsselt Backup hast, die vor...
Da du ja für beide Standorte verschiedene Namespaces nutzt, synct er eh nur benötigte Chunks der jeweils lokalen backups und wie vor mir geschrieben wurde, werden bereits vorhandene Chunks nie noch einmal übertragen.
Hi, ja, ist genau wie du vermutest. PBS checkt vor dem Sync, welche Snapshots bereits auf dem Ziel vorhanden sind, und überspringt sie. Der Rücklauf B→A würde daher quasi leer durchlaufen.
The way COW works, the 2:2 parity data is still on the zpool after you 'move it out', and still being used to calculate the total space of the pool. You need to actually replace that data with 2:4 parity data so it calculates with that. 1.35TB...
But RAID5/6 probably does not give good performance (in terms of IOPS, which you need for multiple VMs trying to use the drives at the same time). I though I mentioned that in my post.
Ich bin nicht der OP, aber ich antworte dennoch mal..., nur zu Unterhaltungszwecken...
Naja..., warum nicht so arbeiten?
Ich verwende PVE extensiv an mehreren Stellen, in meinem Keller läuft ein (total oversized) Cluster. Mit den üblichen...
Hello Udo,
Thank you very much for the explanation. I use the datastore for VMs only; static data is stored on a NAS with HDDs.
From this, I conclude that I should probably use RAID10 (i.e. 6x mirror vdevs) for performance reasons as well...
You did not say anything of the underlying filesystems...?
For ZFS it may be expected as ZFS does a lot more work than classic filesystems under the hood, resulting in multiple IO-operations used for metadata etc...
The deprecation itself was not strongly influenced by that, but the decision to communicate it more actively was in fact primarily driven by it. Normally, we only mentioned it on the side once a new kernel became the default. In the past, we...
Well..., it is "50%" versus "66%". For this 16% more space you lose two third of available IOPS. Six mirrors have three times the IOPS as two RaidZ2 offer, every single vdev counts.
If you are storing VMs on the resulting pool then this is...
There was or there is an error in capacity reporting. I have no link, but the main point was that "more capacity" was actually present but just not reflected by the displayed values.
As you found your solution by recreating the pool you may...
After expanding the RAIDZ2 you need to rewrite the data so it can use the new parity ratio of 2:4 instead of 2:2.
See: https://openzfs.org/w/images/6/68/RAIDZ_Expansion_v2.pdf and...
Proxmox does not automatically check for filesystems (that you create using command-line tools or otherwise). Go to Datacenter -> Storage and click Add and then ZFS. There you can select your new ZFS pool and give it a name and tell PVE how you...
It should actually show up in node > Disks > ZFS. I'd recommend you enable the Thin provision option when adding it as storage. It's named a bit counter intuitive but it affect the refreservation property preventing you from over-allocating...
You can know this if /run/reboot-required exists. Usually only when a new kernel was installed.
See: https://forum.proxmox.com/threads/on-package-updates-how-do-you-know-when-a-reboot-is-required.156352/