SQL Server DR testing using XIV SAN replication.

We are testing DR against SQL Server 2008 with XIV replication on our IBM SAN. The O/S, MSSQL, and data drives are all being replicated.  Our process includes setting up the replication, then shutting down the servers, assigning the mirrored LUNs to failover servers, and then booting up the failover servers.

Can anyone recommend a test against SQL Server that might break our system?

We have successfully tried online index rebuilds and normal index rebuilds.  High volume bulk inserts were also succussful.
LVL 7
lundnakAsked:
Who is Participating?
 
Ryan McCauleyData and Analytics ManagerCommented:
What's the lag time on your replication? The only concern I'd have is that a transaction may have been committed to disk on the primary SQL Server, but then when you boot up the server attached to the mirrored LUN segments, it's in a different commit state, since things haven't been fully replicated over yet. If your servers are located in the same physical datacenter, you may want to consider Windows Clustering as a failover option - the two servers share a single set of LUNs and the OS handles who is in control and responding to client requests.

Other than that, your system sounds like it will work, and the replication lag is the only thing I can think of that would jeapordize the stability of your system. If your server is in production already, then your ability to simulate a failure is limited, but you can try cutting the network connection to your standby server as soon as a very large transaction commits in your primary server (but before replication is likely to be complete), and then attempt to fire it up and see what the state of the data is.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.