Re: Standby server - with no data loss

From: Mike Epprecht \(SQL MVP\) (mike_at_epprecht.net)
Date: 12/28/04


Date: Tue, 28 Dec 2004 15:53:29 +0100

Hi

Stuff like EMC's SRDF is good, but data movement is done at large block
level (typical 512k buffers), so but if you loose the EMC, you might not be
transitionally correct (or worse, DB corruption).
Also, relying on EMC, if the DB goes corrupt, the corruption is replicated
to the DR system.
We use EMC's SRDF for massive banking systems, but we are aware that tape
backup might be our last resort.

The closest you can get is Log Shipping at 1 minute intervals.

If you can hang on until next Summer with log shipping, SQL Server 2005 has
Database mirroring which will be 100% point in time correct.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"AnthonyThomas" <Anthony.Thomas@CommerceBank.com> wrote in message
news:#Sup$FO7EHA.3836@tk2msftngp13.phx.gbl...
> If you are running a Fail-Over SQL Server cluster, then you are using some
> sort of Shared SCSI, perhaps a SAN? If so, then talk to your SAN rep;
most
> have a mirroring feature, both snapshot and real-time mirroring, that
would
> allow you to replicate an off-site disk mirror. Connect that to an
offsite
> server and you would have a DR standby solution.
>
> Short of this, you're only other fail-safe is the backup strategy. Make
> sure you make you Full Database and Transaction Log backups to an
off-server
> disk, then make backups of those files to tape that are kept off-site.
>
> Sincerely,
>
>
> Anthony Thomas
>
>
> --
>
> "Ravit" <Ravit@nia.co.il> wrote in message
> news:09ec01c4ecdb$612d05b0$a501280a@phx.gbl...
> Hi,
>
> We are planning a recovery plan for a database, using a
> standby server.
> ( this database already have a failover cluster )
> the needs in case of a failure are:
> to go up as soon as possible,
> and most important - not to loose any transactions
> already commited.
>
> i checked all the documented features : transactionl
> replication, and log shipping.
> log shipping seems good, and easy to maintain - but i
> doesn't ensure no data loss.
>
> can anyone light my eyes about a solution i missed
> through my reading ?
> maybe it is just a littlie feature i don't know about,
> or a third party tool,
> or a script someone wrote.
>
> Thanks in advance,
> Ravit.
>
>



Relevant Pages

  • Re: Having more copies of backup log file
    ... Using log shipping, SQL Server will not by itself copy the backup to two locations. ... When i restore i want to use ...
    (microsoft.public.sqlserver.programming)
  • Re: Attach Database
    ... Log shipping can be performed with any edition, you just cannot just the built-in stuff in EM and Maint wiz ... Tibor Karaszi, SQL Server MVP ... > hours every night and restoring on the backup server. ...
    (microsoft.public.sqlserver.server)
  • Re: Clustered SQL servers in DR Hotsite
    ... DB mirroring is still an option without going to EE, ... SQL Server MVP ... the initial synch involves taking a full backup. ... here could be changed to point up to the hotsite. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Having more copies of backup log file
    ... Tibor Karaszi, SQL Server MVP ... But if Checco is using Ent.Ed then he could implement it easily. ... >> Using log shipping, SQL Server will not by itself copy the backup to two ... You still have backup to ...
    (microsoft.public.sqlserver.programming)
  • Re: Best Replication Type please
    ... I would love to use Log Shipping, ... file backup, if that the case then the backup we have in ... SQL Replication is not very friendly about Schema ... >I support the Professional Association of SQL Server ...
    (microsoft.public.sqlserver.server)