Your company has a Microsoft Hyper-V Server 2008 R2 environment. You manage the
environment by using Microsoft System Center Virtual Machine Manager (VMM) 2008 R2.
You plan to install 3 host servers and 15 child partitions in the virtual environment. You will
perform child partition placements by using SAN migration. You need to place the
appropriate number of child partitions on each logical unit number (LUN) to support SAN
migrations. How many child partitions should you place on each LUN?
A.
1
B.
3
C.
5
D.
15
Explanation:
Live migration overview
Live migration is a new Hyper-V feature in Windows Server 2008 R2, which requires the
failover clustering feature to be added and configured on the servers running Hyper-V.
Hyper-V and failover clustering can be used together to make a virtual machine that is highly
available, thereby minimizing disruptions and interruptions to clients. Live migration allows
you to transparently move running virtual machines from one node of the failover cluster to
another node in the same cluster without a dropped network connection or perceived
downtime. In addition, failover clustering requires shared storage for the cluster nodes. This
can include an iSCSI or Fiber-Channel Storage Area Network (SAN). All virtual machines
are stored in the shared storage area, and the running virtual machine state is managed by
one of the nodes. Cluster Shared Volumes are volumes in a failover cluster that multiple
nodes can read from and write to at the same time. The nodes coordinate the reading and
writing activity so that the disk is not corrupted. In contrast, disks (LUNs) in cluster storage
that are not Cluster Shared Volumes are always owned by a single node. Cluster Shared
Volumes have the same requirements as non-Cluster Shared Volumes disk resources. The
storage location in the Cluster Shared Volumes is under ystemDrive/ClusterStorage. When
creating the virtual machine, we recommend that you use this storage location. Cluster
Shared Volumes can only be enabled once per cluster.
