Search results

I've got multiple clusters and want to be able to migrate guests between them. This is already possible for some time via "qm remote-migrate" or via backup+restore but after migrating the guest, it's firewall rules won't work any longer unless you make sure each clusters aliases + IP sets +...

Ich persönlich bin auch Freund von Raid für alles. Egal ob im Homeserver, GamingPC, Laptop oder was auch immer. Nicht unbedingt, weil ich daheim die permanente Uptime brauche, sondern weil ich einfach zu faul bin da ständig alles von Grund auf neu aufzusetzen und mir dann die Wochenenden mit...

It will become slower. Both ZFS and SSDs in general need free space for full performance. Mixed block sizes (like ext4 in VM writing 4K blocks to a 512B virtio disk to a 16K Zvol), nested filesystems, sync writes that can't be cached without PLP so consumer SSDs won't be able to optimize writes...

Problem isn't the amount of logs but the write amplification. So 50GB of writes (mostly logs and metrics) inside the VMs gets amplified by factor 20 to 1TB of writes to the physical NAND of the SSDs. Also depends how you store your logs. All my metrics and logs gets written to DBs (zabbix with...

Alle Daten ALLER Backup Snapshots sind dedupliziert. Du brauchst also alles was der PBS je gespeichert hat. Sprich alle Backups von Allem, also deinen kompletten Datastore-Ordner mit den Millionen über Millionen von Chunk Files in zehntausenden von Unterordnern. Weil Backups von verschiedenen...

Ja, das geht prinzipiell. Solange du deinen kompletten Datastore noch fehlerfrei vorliegen hast und du ggf. deinen Encryption Key gesichert sofern Verschlüsselung aktiv ist. Du hast aber echt viel Downtime da erst einmal alles neu aufzusetzen. Auch das Ändern der Ownership von all den Bakup...

You don't. I just hope most people are running those servers air-gapped and not to host some webservers. But probably it's more like a case of "never change a running system".

Node uptime. See some peoples posts asking for support: Here for example 1264 days of node uptime running kernel 4.13 in 2023 ;) https://forum.proxmox.com/threads/permission-denied-error-for-vzdump-command.130885/#post-574612

Why not? Did you test it? Its not uncommon here that I'm able to read/write faster to/from my pool than the hardware would allow. You just need lots of well-compressible data. See for example some LZ4 compression benchmarks: If my SATA protocol can handle 550MB/s but my CPU can decompress with...

No experience here with that specific hardware. But as a rule of thumb: If the hardware supports the latest Ubuntu LTS and Debian it should also run PVE. Because PVE is based on Debian but uses the Ubuntu LTS kernel. So you might want to have a look if that servers hardware is on the Ubuntu...

One problem might be missing RAM defragmentation when you never swap out data from RAM to disk and later back but reordered/compacted. You might end up with "free" RAM that can't be used because it is too fragmented and then OOM killer kicks in while still having lots of free RAM left that can't...

There is a dedicated storage for virtual disks (so not stored on the failed system disk)? Did you create a backup of your "/etc/pve/qemu-server" folder on your OS disks root filesystem? Or is that PVE server part of a cluster? Or do you have some VZDump/PBS backups of those VMs? Because the VMs...

It's not always about if your data is still there after 10 years. Another question is, if the data is still the same after all those years. Without ECC and some checksumming filesystem like ZFS you will never know how much of your data corrupted over all those years. Lets say you stored 100...

No idea. I personally would have coded it with such an option and also with a MAYBE useful default blocksize preselected depending on the pool layout and number of disks (like TrueNAS does it). Only possible by destroying and recreating that zvol (so for example backup+restore of a VM). 4K is...

See the first post where I quoted @wbumiller (one of the PVE staff members): But I never got an answer if this only happens to swap on virtual disks or to swap on physical disks as well.

No, never found a good solution. :/

And you should use something like this to tell PVE that "/mnt/backup" is a mountpoint so it won't try to write backups to the local storage in case that folder isn't mounted: pvesm set <IdOfYourDirectoryStorage> --is_mountpoint /mnt/backup

Maybe your root filesystem is full as well? This could cause the webUI to fail becasue of a read-only filesystem. You could check that via CLI with "df -h" and look for the like with the single "/" if it is at 100% utilization.

Man kann einen beliebigen Ordner vom Host per Bind-Mounts in verschiedene LXCs bringen. Dann könnten beiden LXCs auch gleichzeitig auf den selben Ordner zugreifen. Macht aber nur Sinn, wenn du keinen Cluster hast, da du dir sonst nervige Abhängigkeiten einfängst. Auch kann es mit den Rechten...

Thanks for the hint. I will see If I will write a new tutorial once I find some time to update my Piholes to v6.