Looking for some real world advice for disaster recovery
Currently we have 2 physical sites  about 300 miles apart with a 500mb com link between the 2 sites
We have approximately 20 virtual servers that make up our production services including sql, exchange, share point and other Microsoft servers all running windows 2008r2 operating system utilizing hyper-v
Our San storage is based on dell,s

Anyone have some thoughts on what can be used for failover
We would like to bring DR site within 2 hrs of failure at primary
We also have about 35tb of data on the primary site
We are looking to replace current dr solution for somethimg that is extremely reliable and ease to execute
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gerald ConnollyCommented:
With a 500Mbit link you are better prepared than most people who ask this kind if question.

You should be able to replicate your data across that link OK, depending on the volatility of your data.
BUT the problem is going to be because of your 35TB of data, the initial silver of the mirror and the failback to the primary after an error.

500Mb/s = 50MB/s which means that it will take 195 hours or just over 8 days to move all that data
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Check with Dell as some SANs allow replication.  What you could do is ship a full backup of your data, restore it at the other site and then let the SANs synchronize.  Without the ability tot perform a restore and then a sync, my guess is that your data will require at least two weeks as a minimum to synchronize  (real world scenario).
When setting up a DR site, the initial copy of the data can be a challenge. The amount of bandwidth needed between the two sites for data synchronization on a daily basis is a lot less than that which would be needed for the initial seeding.

One way around this is to have the data storage array to be used for DR initially delivered to the main site and set up there where the seed copy can be accomplished at LAN speeds. Then the array can be shipped to and installed at the DR site.
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

porto111Author Commented:
We already have all the data at tgeDR site
My question is more on how and which technologies to use to keep the 2 sites in sync
Looking for a reliable DR solution to replace the one we use now which is software based at server level but it's not stable enough
porto111Author Commented:
As an example how do we keep the databases in sync between the 2 sites
Maybe sql replication?
What about the exchange servers?
Application and file servers?
All other servers?
It's a puzzle, isn't it?

Do you work with the application's built-in replication mechanisms (DAG for Exchange, SQL replication)?

If everything is located on a storage array, the vendor may have a method for replication that is sensitive to the issues of database consistency for SQL and Exchange.

Otherwise there are third-party products (I've used Double-Take in the past), which - for additional money - will handle Exchange, SQL, and VM replication. You can get a one-stop solution that will promise to give you automatic and nearly instant failover, with little or no downtime, in the face of a variety of potential disasters.
Gerald ConnollyCommented:
how do you keep the 2 sites in sync?

Firstly you need to consider your RPO/RTO objectives.
Because, as your Fail-Over times decreases, the cost of providing that reduction, increases.

If your fail-over time is measured in hours, you could consider log shipping, etc; but if it is measured in minutes then, either hardware or software replication is probably where you are at. Using HW replication will get you closer to real-time but at increased cost to a software solution.
But replication brings its own headaches as you still have to do the initial silver-of-the-mirror aka seed load, is still required (even if you already have the data at the DR - it won't be in the correct format). As I posted earlier and Mohamed & Jcmg confirmed, it's going to take far too long to do this initial sync across your link, more importantly it's far too long to fail-back after a disaster. So whatever plan you put into effect you need to add the constraint of moving all that data between the two data centres.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Disaster Recovery

From novice to tech pro — start learning today.