Post reply

Log Shipping Overhead - Documentation Needed

  • April 23, 2007 at 4:49 am

    #123551

    Can someone point me to a documentation regarding server overhead on log shipping?

    Here's the situation.   I have a cluster that is SQL Server 2000 Sp4 that has 229 databases on it ranging in size from a few meg to 50G in size.  It has 2 CPUs and 4G of RAM.  Total space is about 160G when all backed up.  We need to move that data from a data center up in Massachusetts to new server in Texas.  The customer wants us to keep things in sync until the cutover date which is about 6 weeks from now so there is no more than an hour outage during the cutover.   Also in this mix is a version upgrade on the target to SQL Server 2000 SP4 - 64-BIT. 

    The customer keeps harrassing me about setting up log shipping on the databases from point a to point b.   My contention is the overhead that log shipping that many databases would put on the current production box that has limited resources, but I cannot test it at all.   We used a product over the weekend called Double-take to try the sync and about 2 this morning it caused the cluster to hang.    Also in this mix the customer wants the ability to test for a 3-week period prior to cutover on the destination databases. 

    What would you do?

  • April 25, 2007 at 2:49 am

    #702317

    No one else has had a go, so I will try to help.

    I use log shipping all the time.  It is lightweight and works effectively.  That said, I always roll my own - I don't use MS/3rd party tools for it.

    Assuming you have full recovery model db and are backing up the transaction log anyway, the only overhead associated it copying the tlog backups off the server to somewhere else.  If you aren't already backing up your transaction logs, then this may be a problem for you. 

    For what its worth I logship well over 40GB/Day over about 200 miles.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply