Disaster Recovery Options

Hi Gwen,

We recently built a complete Tessitura system for disaster recovery at our colo, in case our in-house data center encounters major issues. I'm using mirroring to keep the dr database up to date. Mirroring is running very quickly and smoothly across a VPN tunnel to the colo. We're not using a witness server, so cut-over to the DR site is a manual process. I set it up that way because of a number of configuration/database changes that have to be made in order for Tess to be usable. Once everything is set up (about a 1 hour process) our end users can access Tessitura at the DR site via RSA authentication into a Terminal Server.

If you have any questions about it, please feel free to ask.

Jeff

Thanks for the response! Are you using SQL Server 2008 Enterprise? We currently have Standard, so I don't think the asynchronous db mirror is an option for us, and if I understand correctly, synchronous mirror would require a witness server? I was thinking though that the failover process would require manual input to make configuration changes.

Hi Gwen,

We are considering transaction log shipping to a remote server for disaster recovery.  We currently have our transaction log backups running every 15 minutes are are thinking in terms of cost / benefit we'd be willing to potentially lose 15 minutes worth of data rather than go through the expense of buying SQL Server Enterprise licences.

If we had a DR event we would redirect the client to the remote SQL server just as mentioned in the mirroring method.

Sorry for the long delay in responding. This holidays struck!

We are using SQL Server 2008 R2 Standard and are mirroring in synchronous mode with no witness server.

Thanks for the feedback, it's very much appreciated! I think we may be going along this route. All the best for 2013!

Thanks for the info Simon, we may use the mirroring option, still looking into it though. All the best for the New Year.