Hi There,
Hyper-V can use different types of storage and methods of storage connectivity and configuration.
While keeping in mind on shared configuration plan, Microsoft Server Hyper-V 2016 running on the HPE Server with MSA SAN 2050 supports shared storage either via Fibre Channel or iSCSI.
Since we are talking on the Hyper-V side, it is essential to think through both HYPER-V Node level storage provisioning and Virtual Machine Level Storage provisioning.
CSV shared volume can host all the VMs running on the Hyper-V Cluster nodes to which the CSVs are presented. But, when deploying VMs and VHDs to CSVs, it is not a best practice to create a single large LUN or logical disk to hold all virtual machines. Besides, It is better to separate the VM System files and the VM Disk files at the LUN level. Create the VHD on the appropriate CSV volume.
Moreover, as you mentioned about restore of VM from snapshots; if it operates at the individual LUN level, and when checkpoint should fill all available space, only the virtual machines sharing that space will be affected.
Other benefits that you achieve doing so will grant you the flexibility to use Storage Live Migration to address changing needs. For example, moving virtual hard disks into a fresh space automatically defragment them.
Furthermore, many hypervisor-aware backup solutions can leverage hardware snapshot providers, which will operate at the LUN level. Separated LUNs means smaller snapshots and quicker operations.
Microsoft makes additional recommendations with Hyper –V and failover clustering. Thus, it is also recommended you adopt all best practices described in the MSA best practice document according to the MSA model in use to ensure supportability and maximum performance.
Hope this information help!