S2D storage for the VM's
- Thread starter att
- Start date
I don't get if you just want to use
- two totally independent machines
- two machines with a shared disk
That's inside ... I want to know the outside to answer your question.
Do both nodes need to access the same storage or not? So, is S2D a distributed shared storage system or a dedicated shared storage system.
If it is the later - so every box has it's own disk - then you will not have any problem with PVE, just install the two windoze boxes and do whatever you need to do inside to create the storage. If you need a shared disk you may need some CLI work.
Let us know how that works out. I vaguely remember Windows being picky about what devices are allowed to be used, so it may frown upon virtual disks...
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Code:
Storage Hardware. Storage Spaces Direct requires 2 and up to 16 Microsoft-approved servers with direct-attached SATA, SAS, NVMe, or persistent memory drives that are physically attached to just one server each. Each server must have at least two solid-state drives, and at least four more drives. The SATA and SAS devices should be behind a host-bus adapter (HBA) and SAS expander.Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
ok, thanks! will do. s2d technology is picky. in some other hypervisors physical s2d pools presented to VMs works fine, ant virtual disks pools not. Thats why I tried to ask about it in Proxmox.
It is possible although with several nuances. Each machine in the cluster has to have a minimum of 4 disks that you have to add with SATA (the only option to install it), activate the cache in write back and the SSD emulation option.
It would also be necessary for each disk to be assigned a different serial number than the one given by Proxmox because it will be repeated on other machines and s2d does not like that since they have to be unique identifiers, an option that it does not have in the GUI. You have two options to assign a serial number, with qm set or by editing the machine configuration file that can be found in /etc/pve/qemu-server/
The latter would be the fastest, as follows:
sata0: pool1:vm-138-disk-1,cache=writeback,serial=vm138000,size=100G,ssd=1
sata1: pool1:vm-138-disk-2,backup=0,cache=writeback,serial=vm138001,size=2T,ssd=1
sata2: pool1:vm-138-disk-3,backup=0,cache=writeback,serial=vm138002,size=2T,ssd=1
sata3: pool1:vm-138-disk-4,backup=0,cache=writeback,serial=vm138003,size=2T,ssd=1
sata4: pool1:vm-138-disk-5,backup=0,cache=writeback,serial=vm138004,size=2T,ssd=1
Backup=0 is that we skip these disks in the backup, since it is not interesting to backup the replicated disks, only the OS, for file-level data other options are better.
It would also be necessary for each disk to be assigned a different serial number than the one given by Proxmox because it will be repeated on other machines and s2d does not like that since they have to be unique identifiers, an option that it does not have in the GUI. You have two options to assign a serial number, with qm set or by editing the machine configuration file that can be found in /etc/pve/qemu-server/
The latter would be the fastest, as follows:
sata0: pool1:vm-138-disk-1,cache=writeback,serial=vm138000,size=100G,ssd=1
sata1: pool1:vm-138-disk-2,backup=0,cache=writeback,serial=vm138001,size=2T,ssd=1
sata2: pool1:vm-138-disk-3,backup=0,cache=writeback,serial=vm138002,size=2T,ssd=1
sata3: pool1:vm-138-disk-4,backup=0,cache=writeback,serial=vm138003,size=2T,ssd=1
sata4: pool1:vm-138-disk-5,backup=0,cache=writeback,serial=vm138004,size=2T,ssd=1
Backup=0 is that we skip these disks in the backup, since it is not interesting to backup the replicated disks, only the OS, for file-level data other options are better.