<div>
<blockquote>
I understand that the HV Replica scenario is more suited to DR
</blockquote>
<br />
we would agree, in the event a VM fails on Production Server, you can quickly turn on the Replica.<br />

<blockquote>
<br />
rather than BC and to do HV clustering we would require a centralised data storage -i.e. SAN. 
</blockquote>
<br />
Failover clustering does require the prerequisite of centralised data storage, this could be SMB3 file share, not necessarily a SAN.<br />
<br />

<blockquote>
To keep their costs down their Internal IT have asked if we can migrate all their VM's to 1 physical server (Currently &nbsp;split over 2 servers) and then setup a separate 10Gbit link directly between the 2 servers and use the second server as the HV replica - setting a low replication time to reduce data loss. 
</blockquote>
<br />

<blockquote>
Does anyone have any thoughts on this?
</blockquote>
<br />
Well that works, it depends on, on how much value, they give to lost business, with time taken to spin up the replica, and also data loss, between the last replication time.<br />
<br />
and finally -<b> Customer/Client is always right!</b><br />
<br />
<i>We do what we are told</i><br />
... <i>Milgram's 37</i>
</div>


<div>
workable but there is approx 15 minute lag
</div>


<div>
15 minute lag is not a problem - within 2 hours is reasonable with minimal data loss in the event of major hardware failure
</div>


<div>
So there you go, but have a read of Cliffs post!<br />
<br />
You may want to re-think!
</div>


<div>
Thanks Cliff<br />
<br />
There are 3 virtual servers with 1 of these being SQL. Currently emails are with O365 so no onsite exchange server. IF we went for shared storage - i.e. SAS enclosure would this technically be a dual port DAS connected to both servers or would it work OK SMB3 via 1GB ethernet?
</div>


<div>
<div class="content wysiwyg-content">
We have been asked by a customer to setup Hyper-V Replica internally on 2 servers as part of their improved Business Continuity plan.<br />
I understand that the HV Replica scenario is more suited to DR - where the Production site may be unavailable, rather than BC and to do HV clustering we would require a centralised data storage -i.e. SAN. To keep their costs down their Internal IT have asked if we can migrate all their VM's to 1 physical server (Currently &nbsp;split over 2 servers) and then setup a separate 10Gbit link directly between the 2 servers and use the second server as the HV replica - setting a low replication time to reduce data loss. Does anyone have any thoughts on this?
</div>
</div>


We have been asked by a customer to setup Hyper-V Replica internally on 2 servers as part of their improved Business Continuity plan.
I understand that the HV Replica scenario is more suited to DR - where the Production site may be unavailable, rather than BC and to do HV clustering we would require a centralised data storage -i.e. SAN. To keep their costs down their Internal IT have asked if we can migrate all their VM's to 1 physical server (Currently  split over 2 servers) and then setup a separate 10Gbit link directly between the 2 servers and use the second server as the HV replica - setting a low replication time to reduce data loss. Does anyone have any thoughts on this?

Query on LAN based Hyper-V Replica Server 2012 R2

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.

Server Hardware

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.