Hello, I am Henry and I want to share my insight about your concern.
First off, could you help clear up a few things:
What version of Windows Server will be running on your Hyper-V hosts?
How is the SAN connected to the servers (i.e., iSCSI or Fibre Channel)?
For your scenario with two servers and a single shared SAN, the correct and most powerful technology to use is Failover Clustering, not Hyper-V Replica.
- Hyper-V Replica: Is designed for Disaster Recovery (DR). It creates a copy of a VM on a separate, independent storage location (like a second SAN at another site). It's not meant for use with shared storage. https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831716(v=ws.11)#uses
- Failover Clustering: Is designed for High Availability (HA). It allows multiple servers (nodes) to work together using shared storage. If one server fails, the cluster automatically starts its VMs on the other healthy server. The VM's data doesn't move because it's already on the shared SAN accessible by both hosts.
Regarding your Domain Controllers: Just ensure your cluster can start and authenticate properly in a scenario where the DCs are initially offline (which is a default capability in modern Windows Server).
I hope this information and these keywords help point you in the right direction for your research. If you'd like implementation steps, just let me know.