asked on
Disastercrecovery
Hello
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
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
Disaster RecoveryNetwork ArchitectureStorage SoftwareDell
Last Comment
Gerald Connolly
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.
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.
ASKER
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
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
ASKER
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?
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.
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.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
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