SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SAN to SAN hardware level (Block Level) replication solution for MSSQL 2008 R2 databases...


SAN to SAN hardware level (Block Level) replication solution for MSSQL 2008 R2 databases synchronization between DR and Production

Author
Message
ali.siddiqui 79140
ali.siddiqui 79140
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 4
Hi;

Appreciate your suggestions and solution for following scenario

Scenario:
======

1) My SAN team already implemented SAN to SAN replication between disaster recovery and production site
2) SAN to SAN replicaiton solution is hardware level/block level replication solution provided by vendor
3) I have one MSSQL 2008 R2 cluster at production site and one MSSQL 2008 R2 cluster at disaster recovery
4) MSSQL databases mdf and ldf files are on SAN storage

Q1 - As per above scenario, Will it transfer databases mdf and ldf files from production SAN to DR SAN, or is there any complexity to synch mdf and ldf files by using SAN to SAN hardware level\block level replication?
Q2 - In case of production failure can I attach database mdf and ldf file at DR site? or Is there any extra step will be required to attach mdf and ldf file
GilaMonster
GilaMonster
SSC Guru
SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)

Group: General Forum Members
Points: 86288 Visits: 45232
First ensure that the SAN replication preserves write order and is certified to work with SQL Server databases. If not, then you've got a russian roulette DR solution there. Also make sure that the latency on the replication does not result in unacceptably slow IOs on the production server.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


BuntyBoy
BuntyBoy
SSC-Addicted
SSC-Addicted (492 reputation)SSC-Addicted (492 reputation)SSC-Addicted (492 reputation)SSC-Addicted (492 reputation)SSC-Addicted (492 reputation)SSC-Addicted (492 reputation)SSC-Addicted (492 reputation)SSC-Addicted (492 reputation)

Group: General Forum Members
Points: 492 Visits: 405
In our environment we are not preferring this scenario and would rather request to opt out the mdf. ndf and ldf files as it have caused issues during DR exercise....

===========================================
Better try and fail than not to try at all...

Database Best Practices

SQL Server Best Practices
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search