Is there a set percent of the L2 cache that is dedicated to read cache vs write buffer in StarWind? For instance I think VMware vSAN's cache drives are dedicated 70% to read cache and 30% to write buffer.
A user at Spiceworks said currently the target goes offline and you manually disable the cache to bring it back online. There is a feature request to make it disable cache automatically.
Is this fixed in v8 build 7774? https://www.starwindsoftware.com/release-notes-build "LSFS Performance optimizations. Defragmentation issues fixed. In some cases, defragmentation process could stop, and device files take more disk space then required. Currently during the normal operation, devi...
What is the proper way to present the SSD (for L2 cache) to the StarWind VM using VMWare ESXi? Do we just add a VMWare datastore to the SSD and add a virtual disk to the StarWind VM? Or is there a way to pass the SSD through to the VM, either using some passthrough method or RDM? This also brings up...
What is the correct way we should power down a 2-node hyperconverged setup when the power fails and we are on UPS power? The APC software has options to migrate VMs, and also to shutdown VMs, and also to shutdown the physical hosts. The main concern is with the write buffer getting de-staged in time...
When I look under the MPIO Device Details in iSCSI Initiator (2012 R2), I see that not all of the devices are using 127.0.0.1 as the primary path. Should all devices on both nodes be set to 127.0.0.1 under normal conditions until a failover occurs?
If V2V converter had the ability to connect directly to an ESXi host and convert a powered off VM (or even snapshot the VM and convert it while it's online!), that would make the converter MUCH more useful. As is, it takes FOREVER to power a VM off, copy the VMDK off to a Windows host, then run the ...
I know with SAN solutions where they are doing something like LSFS, they say that boosting CPU speed and cores will give you more storage performance. Is that the case with StarWind also? I am wondering if I can stick with relatively low CPU performance (ex. 4-core 2.4 GHz for a storage-only node), ...