<div>
No you don't need to install Hyper-V on Server1 as your SAN is just your storage and your cluster can access your SAN. But you will need file and storage services role. 
 
Yes, you can load the hyper V role on server1 if you want, if you want to utilize another vm. Doesn't have to be clustered, this will just sit outside your cluster.
</div>

<div>
<div class="content wysiwyg-content">
I have in my brand new lab (all 2012 R2)... 
 
* 1 Server with 16 SATA hard drives that I am designating as my SMB 3.0 &quot;SAN&quot; &nbsp; (SERVER1) 
* 3 Hyper-V Hosts (soon to be in a failover cluster) &nbsp;(SERVER2, SERVER3, SERVER4) 
 
My questions: 
 
1. Do I need to load the Hyper-V Role on SERVER1 along with the File and Storage Services Role. 
2. Can I load the Hyper-V Role on SERVER1 just to have another host (and if so should it be part of the failover cluster I will create for SERVER2, SERVER3 &amp;&nbsp;SERVER4?) 
 
Thank you!
</div>
</div>

I have in my brand new lab (all 2012 R2)...

* 1 Server with 16 SATA hard drives that I am designating as my SMB 3.0 "SAN"   (SERVER1)
* 3 Hyper-V Hosts (soon to be in a failover cluster)  (SERVER2, SERVER3, SERVER4) 

My questions:

1. Do I need to load the Hyper-V Role on SERVER1 along with the File and Storage Services Role.
2. Can I load the Hyper-V Role on SERVER1 just to have another host (and if so should it be part of the failover cluster I will create for SERVER2, SERVER3 & SERVER4?)

Thank you!

SMB 3.0 File Server for Hyper-V Failover Clusters

Disaster Recovery is the planning for and creation of policies and procedures related to the resumption or continuation of an organization's functions following a catastrophic event. The term is most frequently used in relation to failure of networks, but DR preparations also include other business systems and personnel considerations.

Disaster Recovery

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.

VMware

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Computer data storage, often called storage or memory, is a technology consisting of computer components and recording media used to retain digital data. In addition to local storage devices like CD and DVD readers, hard drives and flash drives, solid state drives can hold enormous amounts of data in a very small device. Cloud services and other new forms of remote storage also add to the capacity of devices and their ability to access more data without building additional data storage into a device.