SQL Server Replication for Disaster Recovery

It works well, also useful for offloading reporting / BI
Fairly cheap to implement also.


[cid:imagec81c48.GIF@1739f13c.42a86d26]

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Jose Gomez
Sent: 31 October 2012 23:42
To: Vantage
Subject: [Vantage] SQL Server Replication for Disaster Recovery



Hi All

I was wondering what everyone thought about using SQL Transaction Log
Shipping to replicate over to another SQL DB and use as a HOT SWAP when
catastrophic failure occours so that we only loose about 15 minutes worth
of data and we can be up and running in 10 minutes.

VS another regular backup / restore scenario. Has anyone done this?

*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...<mailto:jose%40josecgomez.com>
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*

[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
Hi All

I was wondering what everyone thought about using SQL Transaction Log
Shipping to replicate over to another SQL DB and use as a HOT SWAP when
catastrophic failure occours so that we only loose about 15 minutes worth
of data and we can be up and running in 10 minutes.

VS another regular backup / restore scenario. Has anyone done this?


*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*


[Non-text portions of this message have been removed]
We set up this scenario for an Epicor Enterprise system some years ago where
I led the IT groups. We had the production system at a co-lo and our backup
at our headquarters building, with log shipping over private fiber (co-lo
was a few miles away).



Having such a quick recovery time was a huge plus.



Took a bit to set up, but worked well. We brought in external help to set
it up, then managed it ourselves from that point on. The main downside was
monitoring that the logs were actually getting applied, plus we were
managing two full systems. The tradeoffs seemed worth it.



Cheers,



Jeff





Jeff Greenaway

Consulting CIO/ERP Consultant

jeffgreenaway@...

www.cio-ondemand.com



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Jose Gomez
Sent: Wednesday, October 31, 2012 4:42 PM
To: Vantage
Subject: [Vantage] SQL Server Replication for Disaster Recovery





Hi All

I was wondering what everyone thought about using SQL Transaction Log
Shipping to replicate over to another SQL DB and use as a HOT SWAP when
catastrophic failure occours so that we only loose about 15 minutes worth
of data and we can be up and running in 10 minutes.

VS another regular backup / restore scenario. Has anyone done this?

*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@... <mailto:jose%40josecgomez.com>
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]