Log Shipping backups and Transaction Log backups from Maintenance Plans

  • Hi

    I am currently setting up Log shipping on SQL 2008 Servers. Currently we have an existing transaction log backup schedule running on the databases I want to Log ship. If possible I do not want to disable this job. I know that you cannot have two sets of Log backups running unless you specify the other transaction log backups as COPY_ONLY, but was wondering if I disabled the Backup Job schedule on the Transaction log backup settings, and specified the Network path of the backup folder to be the folder where the transaction log maintenance plans are, would Log shipping work? The secondary server would still be able to copy the log backups from the shared location, the backups are just coming from a differenet source than the log shipping scheduled backup. I have checked the forum and cannot find see this posted before. Can anyone help me with this.

    Best Regards

    Chris

  • If you are going to log ship, the log shipping job should be the only log backup job there is. You are complicating the situation massively. Why don't you want to disable the other maint plan?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • I tested this in my Dev area...the log shipping setup worked (disabling the Backup Job), the copy and restore jobs also work on the secondary server (in the sense they do not fail). The copy job does not copy over the transaction log backups from the transaction log network path. I assume that this is because it does not know what the backups are because they have not been created with the log shipping Backup Job.

    I think you are right I need to disable the current transaction log backup job and set up my transaction log backups using log shipping - the only reason I did not want to do this was because I did not want to interfere with the existing backup strategy if possible.

  • If the existing maint plan is for all DBs, just remove the log shipping one. Otherwise disable it.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Gail Shaw wrote:

    If the existing maint plan is for all DBs, just remove the log shipping one. Otherwise disable it.

    In this case, shall we remove all backups including full and differential for the database uses log shipping from maintenance plan for all? and create a separate plan for full and differential for the log shipping database? There is also a delete files older than in log shipping settings, it is hard to co-ordinate time with the full and differential backup times, and we don't want to delete either full or transaction log backups too early to  break the log chain.

  • Gail Shaw wrote:

    If the existing maint plan is for all DBs, just remove the log shipping one. Otherwise disable it.

    In this case, shall we remove all backups including full and differential for the database uses log shipping from maintenance plan for all? and create a separate plan for full and differential for the log shipping database? There is also a delete files older than in log shipping settings, it is hard to co-ordinate time with the full and differential backup times, and we don't want to delete either full or transaction log backups too early to  break the log chain.

  • Gail Shaw wrote:

    If the existing maint plan is for all DBs, just remove the log shipping one. Otherwise disable it.

    In this case, shall we remove all backups including full and differential for the database uses log shipping from maintenance plan for all? and create a separate plan for full and differential for the log shipping database? There is also a delete files older than in log shipping settings, it is hard to co-ordinate time with the full and differential backup times, and we don't want to delete either full or transaction log backups too early to  break the log chain.

Viewing 7 posts - 1 through 6 (of 6 total)

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