Search results

Are you sure? I have at least one PBS/PVE (installed in parallel on a dedicated node) which has definitely zero IPv6 capabilities. This is all I did to achieve that: ~# cat /etc/sysctl.d/70-disable-ipv6.conf net.ipv6.conf.all.disable_ipv6 = 1

On your picture you see your four mirrors. Each of these is one virtual device = "vdev". They are equally connected to the higher level "rpool". The ZFS term for this construct is "striped" :-) You may easily compare it with a Raid 10.

The basis of everything is "storage". A hypervisor needs many IOPS. (Only) using rotating rust is too slow for nearly everything nowadays. And you are using only one single spindle, as you mentioned. Rebuild your system and use ZFS mirrors only = six mirrors with two drives each. These six...

Damned, you caught me! Absolutely my fault. Terminology I do not use every day...

Am saubersten per Backup und anschließendem Restore mit Angabe einer neuen, konfliktfreien ID. Dies ist vermutlich das einzige offiziell abgedeckte Verfahren. Am schmutzigsten und am gefährlichsten: durch umbenennen der /etc/pve/qemu-server/<vmid>.conf und dem anpassen der referenzierten...

Sieht gut aus :-) Das Pruning markiert Chunks als "wird nicht mehr benötigt". Nach 24 Stunden werden diese Häppchen dann tatsächlich gelöscht - der Speicherplatz wird erst dann wieder frei und steht erneut zur Verfügung. (Nanu, ein Satz war verschwunden): Natürlich werden KEINE Chunks...

Jede Sicherung ist gleichzeitig eine Vollsicherung und sie wird inkrementell erstellt. Das ist die Magie des PBS und der eingebauten Deduplizierung, die es bei klassischen Backup-Datei-Verfahren nicht gibt. Ein Backup Job um 20:00 genügt daher. Und "Aufbewahrung: Tage behalten = 14" genügt...

Step zero: restart corosync on all nodes, one after another: systemctl restart corosync.service ; systemctl status corosync.service Step one: verify that all rings are actually both enabled and connected, similar like this: ~# corosync-cfgtool -n Local node ID 3, transport knet nodeid: 2...

You need to find a metric which quantifies your experience. "Slow" means different things for different people. There are multiple benchmark tools out there... Specifically for storage benchmarks look for "fio". This can be used on the node and also inside a guest. HBA mode is fine. RaidZ1 is...

There are several providers (at different locations) offering this. In my case it is Vodafone, using the (cable-TV) copper network of former Kabeldeutschland. Yes, 1 GBit/s arrives at the end user. And for the large CDNs it does actually deliver this. The problem is, it is massively crippled...

Yes, I use (of course) the same one. It is a CDN, I don't know how to further test it, sorry.

You did not tell us how you are connected to the internet and also hide the country you're in. I am in Germany an I had downloaded >300 MB several times (once per node) during the last hours. There were 42 new packages in the pve-no-sub repository. With my asymmetric DSL I downloaded them with...

Remove one of them, put it into another computer and try to examine/confirm the actual status there.

"Normal" NFS will introduce a single-point-of-failure. With six nodes (and a hope for continuously available services) you might want to avoid that categorical. TrueNAS offers redundant systems. (Not for free, when I looked at it last time.)

Why not test the concrete behavior? Just create a test-Container, add some storage, run backup/restore, "zfs rename" the virtual disk, start the Container, and-so-on. This approach comes for free and teaches you the behavior of your actual system. Just saying... PS: also note that mountpoints...

Things like this is completely "working under the hood" --> yes, there might be dragons. For Proxmox (the software) the configured disk from Container 100 has just vanished. Without further work this will lead to errors of course. I would just edit /etc/pve/lxc/100.conf manually to remove any...

(Usually) successful installation: https://pve.proxmox.com/wiki/Windows_11_guest_best_practices

I did not really read everything here, but you can move a dataset this way: man zfs-rename. Without a snapshot, without cloning.

If you are interested in Load Balancing: https://github.com/gyptazy/ProxLB

You never have enough RAM. And giving only 2 GiB to the main OS is... brave. (I've upgraded some nodes in my Homelab(!) to 128 GiB...) Try to utilize "zram" - it may give you a little bit more free headroom. ~# apt show zram-tools Description: utilities for working with zram zram is a Linux...