1) Can be drive letter or other mount point.
2) L2 Cache is assigned to virtual LUN. There may be or may be not CSV on top. L2 settings are applied during virtual LUN creation process.
3) Yes, you can check cache stats (hit/miss/utilization) in virtual LUN information tab.
4) Yes, you can absolutely share NVMe disk with boot. Except I don't see much point in that (do you reboot on a routine basis to make this process complete faster?)
5) Cache does not need any over provisioning. It's basically a pre-allocated file.
ulaaser wrote:Let me explain what i think i can do:
Hardware:
2 Supermicro servers with nvme support and lsi 3108 raid controller (2 500GB SAS Drives for WIndows 2012R2 Boot Hyper-Cluster and Starwind instalation and 6 1TB SAS Drives for SAN. One 400GB Intel 750 SSD (optional an P3500). 128GB RAM (16GB reserverd for Host OS and lfls)
So what i understand
after installing Windows Server, i create 1 NTFS-Volume based on the 6 1TB SAS Drives (and assign a Letter), and the same for the 400GB SSD (with or without Letter?). And while creating in Starwind the CSV the L2-Cache is created automatically in the background from the SSD using the Size i defined in the Starwind-Assistant?
Is there a way to monitor the usage of the Cache?
As the nvme is super fast, can i use it as Windows boot/Instalation Drive 100GB and also as CACHE 300GB?
About the 200% overprovisioning rule in LSFS (in relation to a NVME SSSD DISK:
Must i consider this overprovisioning also for the 400GB NVME SSD (CACHE) or only for the SAS Drives Volume?