Post reply

Use of transaction logs with a secundary server

  • February 25, 2009 at 9:12 am

    #126667

    Hi

    Can the log shipping configuration of transaction logs use the transaction logs from a maintenance plan or must the plan be deleted? Should the transaction log maintenance plan be stopped bevor the next fullsave occurs, to setup log shipping correctly?

    Thanks for help

    Jan

  • February 25, 2009 at 9:24 am

    #950093

    Hi,

    Typically the way to do this is to disable or alter the maintenance plan. The configuration process for log shipping will create and define a transaction log backup job (certainly on sql 2005).

    That said, provided the transaction log backups are saved to the same folder share, the log shipping copy job will still pickup all the transaction log backups. It just means that your overall configuration will be a little convoluted.

    It is mush easier to have all the transaction log backups managed from one job, i.e. the ls_backup job.

    To answer your second question the transaction log backups from a maintenance plan would continue on just fine after a Full database backup, however again it would be more straightforward to manage the entire process within the log shipping configuration for the given database.

    Hope this makes sense but of course please feel free to pose further queries.

    Cheers,

    John Sansom (@sqlBrit) | www.johnsansom.com

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

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