Re: Disaster Recovery Planning

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Cqlboy (Cqlboy_at_discussions.microsoft.com)
Date: 12/22/04 

Date: Wed, 22 Dec 2004 09:07:03 -0800

Thanx, this was helpful. But I was hoping to have something more explicit
since it appears I'll have to create my DR document from scratch. A template
or example to help guide my thinking and writing would be ideal. I'm not a
technical write, eh?

-Cqlboy

"Mike Hodgson" wrote:

> How long is a piece of string?
>
> DR plans are pretty specific to the company/environment in question.
> I've set up an active/active SQL cluster in our DR site and am using log
> shipping to keep the DR databases in sync with the production DBs;
> combined with MDAC aliases, non-standard TCP ports for SQL & DNS aliases
> for the server names to allow to very quick, transparent redirection of
> client connections to the DR servers in the event of a disaster. I also
> wrote a stored proc (that resides on our log shipping monitor box) to
> automate all the log shipping role changes (150+ databases is a bit too
> time consuming to do manually). Works pretty well too (we had a
> "disaster" in August this year when our SAN vendor stuffed up an upgrade
> on our production SAN - what a crappy weekend that was!)
>
> My only revision to my SQL DR plan/environment would be more RAM & CPU
> for the DR servers as I'm consolidating 4 production SQL instances down
> to the 2 DR instances on the active/active cluster (plus a few other DBs
> that don't live on our production clusters). The cluster nodes were
> pretty stressed for a week back in August but it's hard to justify
> spending the extra $$$ when the servers are really only used (hopefully)
> very infrequently (like one week in a year).
>
> Cheers,
> Mike.
>
> Cqlboy wrote:
> > I've never seen a disaster recovery plan for SQL Server. Can anyone one
> > direct me to an example. This would be immensley helpful to understanding
> > how to put one together. Thanx. -Cqlboy
>

Relevant Pages

  • Re: mirrored sql servers
    ... The I would suggest log shipping. ... >>use it for a production scenario. ... >>Enterprise Edition only, so for these edition replication is about ... SQL Server 2005 will be released with DB mirroring, ...
    (comp.databases.ms-sqlserver)
  • Re: transaction log shipping on a cluster
    ... The cluster does not enter into the Log Shipping picture in any way. ... the Source SQL Server is up, ...
    (microsoft.public.sqlserver.clustering)
  • Re: Replicating Drives to use for Development Instances
    ... with the -S you can write a new Disk Signature:) ... MVP - Windows Server - Clustering ... > site B failover) and a cluster with one node at each site. ... > production and a development instance on the same system. ...
    (microsoft.public.windows.server.clustering)
  • Best practice for DR/Standby server
    ... Production Server and a DR Server that is off site. ... Currently I have SPs coded that do log shipping to the DR ... I've explored Replication, ...
    (microsoft.public.sqlserver.server)
  • Re: Singlr Cluster Node
    ... exchange servers each is located in a seprate and remote place. ... > why you're doing a single node cluster again...is this for Exchange ... > Also, check the Windows Server Catalog, replacing the former Hardware ... Are you talking production ...
    (microsoft.public.windows.server.clustering)