Log-shipping

  • Good afternoon, everyone.  I have a few general questions about log-shipping, and I am looknig forward to your responses.

    1.  What are your thoughts on log-shipping and combining different databases in each maintenance job?

    2.  When you create a maintenance job with log-shipping enabled, the default times set up for transaction log backups, copy and restores, are all the same, unless you change the backup option (12 AM to 11:59 PM, every 15 minutes).  Is it wise to start all the jobs at the same time?  Should you perhaps schedule the backup for 12AM to 11:59 PM, the copy for 12:05 AM to 12:04AM and the restore for 12:10 AM to 12:09 AM?  This puts the standby database 5 minutes behind?

    Thanks.

  • Definitely is wiser to separate them into several jobs and also to space them. That, will give you:

    • Ability to balance the load imposed on the server
    • In case you need to shorten or lengthen the backup interval you have the granularity depending on the activity of each independent database.

     

    Cheers, 


    * Noel

  • Thanks for your reply, Noel.  I guess the question that I'm getting at is if I want my back-up database to be 15 minutes, at most, behind my production database, will having my jobs scheduled below, accommodate that or will it be more than 15 minutes behind?

    The proposed schedule is below:

    1. Transaction log backups, every 15 mins, between 12 AM and 11:59:59 PM

    2. Transaction log copies, every 15 mins, between 12:05 AM and 12:04:59 AM

    3. Transaction log restores, every 15 mins, between 12:10 AM and 12:09:59 AM

    Will having all 3 jobs scheduled to run every 15 mins between 12 AM and 11:59:59 PM cause them to step on each other's feet?  When the backup job starts, the copy job fails 'cause the log file's not ready yet (backup's still creating it) and so on and so forth.

    Thanks.

    Chris

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

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