Your network contains two data centers named DataCenter1 and DataCenter2. The two data
centers are connected by using a low-latency high-speed WAN link.
Each data center contains multiple Hyper-V hosts that run Windows Server 2012. All servers
connect to a Storage Area Network (SAN) in their local data center.
You plan to implement 20 virtual machines that will be hosted on the Hyper-V hosts.
You need to recommend a hosting solution for the virtual machines.
The solution must meet the following requirements:
Virtual machines must be available automatically on the network if a single Hyper-V host
fails.
Virtual machines must be available automatically on the network if a single data center fails.
What should you recommend?
A.
One failover cluster in DataCenter1 and Hyper-V replicas to DataCenter2
B.
One failover cluster in DataCenter2 and one DFS Replication group in DataCenter1
C.
One failover cluster that spans both data centers and SAN replication between the data
centers
D.
One failover cluster and one Distributed File System (DFS) Replication group in each
data center
the requirement is “VMs must be available automatically on the network if a single data center fails.” and “VMs must be available when single Hyper-V host fails”.
the answer B. is wrong because when DC2 fails there is no way to automatically switch on VMs at DC1 where resides only replicas of VMs’ files.
the answer A. is wrong because when DC1 fails then VMs will start at Hyper-V hosts at DC2. But if one Hyper-V host at DC2 fails the VMs from this host will be unavailable. VMs at DC2 have no protection. Disadvantage is that all VMs must be initially placed at DC1 and run at DC1 till failure.
the answer C. is reasonable. SAN replication keeps the VMs data in sync. Then we have shared storage stretched over both data centers. When DC1 fails all VMs will run at DC2, but if one Hyper-V host will fail then VMs form it will be moved to another Hyper-V host in cluster (of course if cluster have enough resources to fail-over VMs). Advantage is that VMs can be placed initially on both datacenters.
the answer D is unreasonable.
0
0
@Wojteck: “the answer A is wrong because when DC1 fails then VMs will start at Hyper-V hosts at DC2 – Agreed with this as VMs in DC2 are replicas and will start when the primary VM fails.
However: “But if one Hyper-V host at DC2 fails, the VMS from this host will be unavailable. VMs at DC2 have no protection” – Disagree – VMs at DC2 re replicas that are meant to be operational when the primary VMs at DC1 fails. So if VMs at DC2 fails, how does this affect the primary VMs at DC1 which continues to run as normal – the only downside being that there will be no failover as the replica VMs are no longer available with failure of DC2.
The correct answer is A.
C is wrong as when DC1 fails, how does a VM in DC1 which has its vdisk in the local datacenter (this is key) knows to use the replicated disk in the DC2? So even though teh single cluster is stretched across two DCs, the disk can only be in one place at a time and the VM can only point to a disk location at a time.
0
0
Ref your last point “VM can only point to a disk location at a time”. You would make the SAN appear as one disk between two sites.
0
0
Agreed it`s C
0
0
Answer is C.
This is the only option that provides seamless VM uptime fulfilling the automatic requirement of the scenario.
Can’t do A because…
Internal site DC1 failures would be automatic but replicas are not seamless for unplanned disaster recovery. Therefore fails on the automatic requirement.
Can’t do B & C because…
All DFS options are out since it does not support replication of active (aka open) files (.vhdx for example). Also B is not failure aware.
0
0
According to the official Microsoft Exam Reference Guide: 412 Pages186,198
Microsoft recommends a Hyper-V failover cluster or a Hyper-V host at one site [DataCenter1] and the Hyper-V replica of those VMs@DataCenter1 at another site [DataCenter2].
This is the Microsoft way. Nothing about SAN replication.
“Hyper-V Replica doesn’t rely on shared storage between the VMs. The replica VM instead begins with its own copy of the primary VM’s virtual hard disk. The primary VM then sends updates of its changes (called replication data and this data is repeatedly saved by the replica VM. Replication frequency is every 5 minutes for Hyper-V
on Windows Server 2012 and either 30 seconds, 5 minutes, or 15 minutes when Hyper-V is running on Windows Server 2012 R2”
My answer is: A
0
0
Peter, I thought Replicas never come online automatically, they always use an administrator to activate them. Considering this, Answer A is not an option.
I would go with Answer C
https://yungchou.wordpress.com/2014/11/17/hyper-v-replica-explained/
1
0
Today, while I was in the office, my cousin stole my iPad and tested to view if it may survive a forty foot drop, so that she is usually a youtube sensation. My ipad from apple is now broken and she or he has 83 views. I know that is completely off topic but I needed to share it with someone!
rca ieftin http://goo.gl/6GqA7S
0
2
The time to read or check out the subject material or internet sites we have linked to beneath.
0
0
below youll locate the link to some websites that we feel you ought to visit
0
0
usually posts some very fascinating stuff like this. If youre new to this site
0
0
here are some hyperlinks to web sites that we link to due to the fact we assume they’re worth visiting
0
0
below you will obtain the link to some web-sites that we consider it is best to visit
0
0
below youll obtain the link to some web sites that we think you should visit
0
0
although sites we backlink to beneath are considerably not connected to ours, we feel they are really worth a go through, so possess a look
0
0
very few sites that occur to become comprehensive beneath, from our point of view are undoubtedly very well really worth checking out
0
0
below you will discover the link to some web pages that we assume you’ll want to visit
0
0
very couple of websites that happen to become in depth beneath, from our point of view are undoubtedly effectively worth checking out
0
0
just beneath, are various entirely not related web pages to ours, even so, they’re certainly worth going over
0
0
one of our visitors not too long ago advised the following website
0
0
one of our guests recently proposed the following website
0
0
here are some links to websites that we link to because we think they’re worth visiting
0
0
please pay a visit to the sites we stick to, which includes this 1, as it represents our picks in the web
0
0
1698 17734Your talent is really appreciated!! Thank you. You saved me a lot of frustration. I switched from Joomla to Drupal to the WordPress platform and Ive fully embraced WordPress. Its so much easier and easier to tweak. Anyway, thanks again. Awesome domain! 615801
0
0
Must be A. It’s a safe assumption that the same subnets won’t exist at both datacenters so the failover must also change the ip address of the replica to one which valid on a subnet at the other datacenter. Hyper-V replication can do this, SAN replication and DFS replication can’t.
0
0