Ok, any feedback now?
We are not really able to estimate gain because of rolling datastore contents, on production PBS... More than 120TiB by datastore...
Thanks,
Christophe.
Clonezilla würde ich mir sparen, das heißt pro VM ein ISO booten, zweite Disk dranhängen, Bootreihenfolge umstellen und hinterher wieder aufräumen. Also genau das Anfassen jeder einzelnen VM, das du ja vermeiden willst, nur mit mehr Schritten als...
Hi, new here and didn't find this thread before posting my own. ( https://forum.proxmox.com/threads/lets-talk-deduplication-and-immutability.182803/ )
But id like to explain how I have managed to use AWS S3 with Object lock to achieve immutable...
Is object lock support on the PBS roadmap? All it has to do is keep a catalog of active chunks and renew their locks on a regular basis.
This is a major pain point for us and is keeping us on Veeam instead of PBS. It's not a "nice to have...
Can you show that? I tried to keep it simple but forgot about hidden paths. Try this
find /mnt/datastore/BRIXBackup/* -maxdepth 1 -mindepth 1 -exec du -shc {} + 2>/dev/null | sort -h
If all the space is taken up by .chunks then, as mentioned...
Hello,
this is a German blog from Dennis Schröder of the installing procedure "Proxmox VE auf dem Raspberry Pi 5: So läuft die ARM-Version..."
Please see:
#...
Automatisiert und ohne jede VM einzeln anzufassen geht das mMn nur, wenn du das Verschieben komplett sein lässt und die ESP stattdessen neu baust. Sprich: Disk hinten per qm disk resize ein paar hundert MB größer machen, im Gast dann per...
Hello all! Thank you for all the replies and suggestions. Yes, our solution is holding up really well so far. We have put in a lot of customizations and measures to all our infrastructure. Upgrades are on their way, without service interruption...
Da ich nun mal einen UltraVNC-Server aktualisiert habe, mal eine Rückmeldung:
Die Geschwindigkeit hat sich massiv verbessert.
Jedenfalls über "Schummelverbindung" per Guacamole.
Man könnte jetzt fast remote arbeiten.
Allerdings funktioniert eine...
Yeah, you're reading it right. Sockets and cores are the maximum topology, QEMU needs that fixed at VM start, so those two fields are greyed out while the VM runs. The only value you can change live is vcpus, that's how many of the max cores are...
That 242 GiB on a 250 GiB virtual disk, with convert not shrinking anything, is the classic "allocated but never released" pattern. Discard enabled in the GUI only opens the UNMAP path from the guest to the image file - it does not free anything...
Please use code blocks, not quotes. I see that you're not using discard. Maybe some of this is useful to you
- https://gist.github.com/Impact123/3dbd7e0ddaf47c5539708a9cbcaab9e3#discard
- https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only.
Proxmox VE 9.2 for arm64...