A company has two offices in New York and one office in San Francisco. There is no shared storage between the San Francisco office and the New York headquarters. AH offices are connected by a wide…

Question

Options

• Aa separate Hyper-V replica between NYC-Host1 and SFC-Host1
• Ba Hyper-V cluster that includes NYC-Host1, NYC-Host2, and SFC-Host1
• Ca Hyper-V cluster between NYC-Host1 and SFC-Host1
• Da Hyper-V replica between NYC-Host1 and NYC-Host2 with an extended replica between

• A
  15% (11)
• B
  7% (5)
• C
  4% (3)
• D
  73% (52)

Explanation

You cannot perform either B or C as shared storage is a requirement for Clustering. However D will work. Unlike "Guest" says an Extended Replica will send all machines to the third site (NYC-1 and NYC-2) because there is a replica between those machines. The extended Replica can also be configured to bring SFC-1 machines back to NYC-1 which will replicate them to NYC-2. Hyper-V Replica Overview Hyper-V Replica provides asynchronous replication of Hyper-V virtual machines between two hosting servers. It is simple to configure and does not require either shared storage or any particular storage hardware. Any server workload that can be virtualized in Hyper-V can be replicated. Replication works over any ordinary IP-based network, and the replicated data can be encrypted during transmission. Hyper-V Replica works with standalone servers, failover clusters, or a mixture of both. The servers can be physically co-located or widely separated geographically. The physical servers do not need to be in the same domain, or even joined to any domain at all. You can configure extended replication. In extended replication, your Replica server forwards changes that occur on the primary virtual machines to a third server (the extended Replica server). After a planned or unplanned failover from the primary server to the Replica server, the extended Replica server provides further business continuity protection. As with ordinary replication, you configure extended replication by using Hyper-V Manager, Windows PowerShell (using the - Extended option), or WMI.

No community discussion yet for this question.