March 1, 2013 at 3:28 am
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
March 1, 2013 at 3:56 am
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
March 5, 2013 at 11:53 am
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....
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply