Best practice is to separate OS and data storage.
So, install OS on small boot drives mirrored. I use ZFS RAID-1. Then rest of drives for VMs/data.
Your future self will thank you.
The recommended place for Bugs and for Feature Requests is over there: https://bugzilla.proxmox.com/enter_bug.cgi?product=pbs
While several Proxmox staff members do regularly use this forum (thank you for that!), that one is considered to be...
Just get a used Dell HBA330 storage controller. Flash latest firmware and Proxmox will use the simpler mpt3sas driver.
I run it in production with both ZFS and Ceph with no issues.
Have you seen the wiki article [0] on full mesh setup methods?
EDIT: As a side note, how stringent are your data consistency needs? As with the amount of data you could also use ZFS with storage replication [1].
[0]...
There is no mentioning of partitioning from my side in this discussion. We mentioned already an existing filesystem, be it exFAT/NTFS/ZFS/whatever. You need to mount that filesystem somewhere.
My second bullet point is "...via Datacenter -->...
There is a new QEMU 10.1 package available in the pve-test and pve-no-subscription repositories for Proxmox VE 9.
After internally testing QEMU 10.1 for over a month and having this version available on the pve-test repository almost as long, we...
Sure, why not?
I have no finished cookbook/recipe for you, there are way too many possibilities. Incomplete steps may include:
mount the SSD "somewhere", make sure it is persistent
integrate its mountpoint as a normal Storage via Datacenter -->...
There is not technical limitation AFAIK, but it is just not very smart.
The root issue is as already mentioned that you have data in blockstorage instead of files.
(at least that is my guess with the limited information you provided).
This comes...
Encryption happens on the client side, and PBS always does a full backup, not differential backups, the re-use of existing data happens through a content addressable storage, not some diffing.
So, due to changing from unencrypted to (client-side)...
genau.
welchen pc du hernimmst ist komplett dir überlassen.
wichtig ist nur, dass du schaust, dass man sie halbwegs mit ram und evtl auch storage erweitern kann.
storage geht dir nämlich auch irgendwann aus, vor allem wenn deine umgebung länger...
Vielen Dank für eure Antworten. Dann werde ich mal schauen was ich damit anfange.
Grundsätzlich spricht also nichts gegen einen Mini-PC von HP oder Lenovo mit einem nicht nagelneuen Prozessor, aber dafür ordentlich RAM, also mindestens 32GB?
That chunk is gone.
The only way to re-create it, is to run a new backup task. If - and only if - the corresponding data still exists on the source side then this chunk will be filled with data again.
Mein reden :-)
Obwohl..., man sollte schon genau hinschauen: Caches/Buffers/ZFS-ARC sind technisch natürlich "verwendeter Speicher", aber notwendig sind sie oft nur in geringerem Umfang, als per Default verwendet wird :-)
RAM ist immer knapp.
Ich betreibe zwei Mini-PCs als Proxmox Nodes, einen Asus NUC 13 mit i5-1340P (in einem Passivgekühlten gehäuse von Akasa) und einen lüfterlosen Minipc von Topton mit Pentium 8505.
Beide Kisten haben 64 GB RAM.
Die CPU's...
Well..., I probably have nothing you want to hear. But here we go:
You don't. PVE is not a generic file server!
There are "hacks" for this. As PVE is Debian you can install any file sharing software you want, e.g. Samba. But again: this is not...
Why did you do this? What's your intention?
The new disks were empty and clean. The PVE installer will handle partitioning very well; if you wanted to give only a fraction of the physical space to PVE: the installer can do this too...
(Usually...