Your network contains an Active Directory domain.
The domain contains 10 file servers.
The file servers connect to a Fibre Channel SAN.
You plan to implement 20 Hyper-V hosts in a failover cluster.
The Hyper-V hosts will not have host bus adapters (HBAs).
You need to recommend a solution for the planned implementation that meets the following requirements:
– The virtual machines must support live migration.
– The virtual hard disks (VHDs) must be stored on the file servers.
Which two technologies achieve the goal? Each correct answer presents a complete solution.
A.
Cluster Shared Volume (CSV)
B.
An NFS share
C.
Storage pools
D.
SMB 3.0 shares
Explanation:
Cluster-Shared Volumes require Host-Bus Adapter (HBA) hardware to be installed on the Physical NIC, so it cannot be implemented here.Scale-Out File Server:
These are active-active File Servers, which means data can be accessed off of multiple File Server Cluster Nodes simultaneously using the “Continuous Availability”
feature in SMB 3.0 – be advised, SMB 3.0 cannot be accessed by clients running Windows 7 or older!
To meet the requirements, we can create a storage pool from the file servers (who will run the Scale-Out File Server Role, using continuous avialability) and then
configure them to host an SMB 3.0 share for the VHDs of the Virtual Machines.
To create an SMB 3.0 Share Across Multiple File Server:
SMB Transparent Failover has the following requirements:
A failover cluster running Windows Server 2012 with at least two nodes.
File Server role is installed on all cluster nodes.
Clustered file server configured with one or more file shares created with the continuously available property. This is the default setting.
SMB client computers running the Windows 8 client or Windows Server 2012.
http://blogs.technet.com/b/clausjor/archive/2012/06/07/smb-transparent-failover-making-file-shares-continuously-available.aspx
I’ll go for:
Cluster Shared Volume
SMB 3.0 Shares
0
0
Agreed. CSV is needed for a Live Migration. A and D would be my answer as well.
0
0
Cluster-Shared Volumes require Host-Bus Adapter (HBA) hardware to be installed on the Physical NIC, so it cannot be implemented here.
Go with C,D.
0
0
So you’d have a SoFS on the fileserver/SAN containing a bunch of VHDXs for the VMs. -> D
I think you’d need a CSV on the SoFS (and so does this chap: https://www.petri.com/how-many-csvs-should-a-scale-out-file-server-have) -> C
NFS is wrong, storage pools is irrelevant
0
0
CSV can be used to implement the iSCSI target from 10 File Servers
Hyper-V hosts can connect to shared storage on iSCSI target
0
0