Post reply

will full backup break log shipping

  • December 23, 2015 at 7:02 am

    #323222

    HI

    Will taking a full backup break a database if it is involved in logshipping ?

    Is there anything i need to be aware of ? - ie shall i change the default location of where it gets stored ?

    Does selecting the 'copy only' remove any danger of things breaking as i believe this leaves LSN's order ?

  • December 23, 2015 at 7:04 am

    #1847716

    No, doing a full backup will not affect the LSN chain so LogShipping will continue to function as needed.

  • December 23, 2015 at 7:55 am

    #1847747

    Thanks very much. For some reason where I work they are saying that in the past backups have broken things...not sure what they have been doing historically.

    Thanks for confirmation though.

  • December 23, 2015 at 8:34 am

    #1847776

    Most likely misunderstanding. Someone might have taken a new transaction log backup at the same time, or had a job that did both and didn't realize it's the log backup that breaks things.

    Follow me on Twitter: http://www.twitter.com/way0utwest
    Forum Etiquette: How to post data/code on a forum to get the best help
    My Blog: www.voiceofthedba.com

  • December 23, 2015 at 4:36 pm

    #1847857

    PearlJammer1 (12/23/2015)

    Thanks very much. For some reason where I work they are saying that in the past backups have broken things...not sure what they have been doing historically.

    Thanks for confirmation though.

    If someone does an ad hoc full backup on a different disk and then loses the backup, that will mean that you have to go one backup further back to do a restore. This is why backup with the "COPY ONLY" option is available. That's probably what they were thinking.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".
    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • December 25, 2015 at 4:06 pm

    #1848087

    COPY ONLY is useful when differential backups are taken. A differential backup cannot be restored unless its full backup is restored first. A COPY ONLY backup will not change the full backup needed by a subsequent differential backup.

  • December 25, 2015 at 9:16 pm

    #1848094

    Full backups do not break log shipping. The only things that cause the log to be truncated are log backups, an explicit truncate or a switch to simple recovery model

  • December 30, 2015 at 2:38 pm

    #1848847

    You should be running regular scheduled FULL DB backups of ALL DBs (this includes LS source DB's) and DIFF DB backups too if needed because you need ALL DBs protected including the Source LS DB. You would not want to have to rely on a very old Full backup file and months of TLog backups to restore a DB if the need arises. Like the other posters stated a TLog backup ran outside of LS will break LS.

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

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