Disaster recovery

WE want to design a disaster recovery solution and would like some feedback on the experts out there
  our environment is a 4 host hyper-v cluster (2012r2) with a dell compellent san
 we have approximately 50 virtual servers on  this cluster- anything from sql to sharepoint, exchange, and everything in-between
 the DR site is 50 miles away and we have a 50mb PIPE connecting the 2 sites

 the DR site has the same san but only 2 host cluster
 we can except up to 10 minutes of data loss, and 2 hours to bring DR site in-case of disaster

 looking for feedback on what others are using out there for disaster recovery

What's wrong with the DR site you have now?

Ideally, you'd have an identical (or nearly identical) environment for your DR site as for your production site.  If that's not practical, scale your DR site to exactly what you need to operate - in other words, your DR site should at least support your mission-critical services.

Since you're a Microsoft shop, Azure might be a solution for you, and has the advantage of being very scalable.

we don't have a DR site as of yet, we are in the beginning phases of designing one
as of now we only have the hardware, that is why we are asking
we want real world ideas on what technologies to use  to replicate data  from primary to DR
etc.

The PIPE should be more then enough to replicate the data between the SAN's and only being 50 miles away latency should be less than 5 ms.

Your setup is ideal and with Asynchronous replication you will always have the data available and with DNS update you will have your servers up in 10 minutes.

what technology is best suited for replicating the virtual machines and applications from one site to another.
im really looking for is ideas on how to replicate data\servers
we have the hardware and pipe in-place but need a way to efficiently sync data so that we can failover and failback

The best method would be by using the SAN replication which then you would have the VHD files in the DR location  and bring them up when doing a DR test -  this would be the replicated copy from the production network -  

here is a sample KB from DELL on the replication and again this product specific

http://en.community.dell.com/techcenter/enterprise-solutions/w/oracle_solutions/4876.how-to-configure-synchronous-replication-between-compellent-storage-centers

Consider Storage Mirroring, sold by HP, or from its owner, Doubletake.  It can provide very rapid failover from site A to site B, with a host of other benefits.

PLEASE NOTE: Solutions like this are NOT a backup solution.  You still need backups to protect against virii, accidental or intentional deletion, corruption introduced by HW or. SW failure, and for historical purposes.

i think everyone is missing the point here, this is for a pure DR site
we have the hardware and the com links all worked out.
what we need advice is on how to replicate the 30 virtual severs that make up our system to this new DR site.
example>
how do we keep our database servers, application servers, file servers, etc. in sync with the ones in the DR site
so that we can switch our services to the DR site if needed to switch over to DR site,

what are others doing out there for this
looking for what others are using and hopefully come up with a solution that is efficient , stable, little performance impact on the production services, asyncronous,

> how do we keep our database servers, application servers, file servers, etc. in sync with the ones in the DR site
> so that we can switch our services to the DR site if needed to switch over to DR site,

DoubleTake (or Storage Mirroring, as sold by HP) will do what you need.
Those functions are exactly what it's designed to do.  Turns out it's now owned by Vision Solutions (or the parent changed its name).
http://www.visionsolutions.com/products/windows/double-take-dr/overview

Understood about your DR setup - Like I mentioned SAN replication is the solution - one example  is NetApp snapmirror replication  and can be replaced with any SAN replication - one prerequisite is your data has to reside on the SAN.

yes but if you just replicate the storage how do you bring up the virtual servers on the DR site?

Basically they way it would work be that you VM's will reside on the SAN on the Prod side and will replicate the data to the DR SAN, and during the DR since you will have your hosts up and running in the DR side, you would just stop the replication and browse to the DR storage and bring the VM's up