Does one failed log backup due to Error 8198 break the log chain?

  • Hello,

    Sorry if this question has been answered elsewhere in the forums. I think it just may be a hard question to search for given that it has many different common SQL terms but not necessarily all in one topic.

    My question is, if we have a log backup schedule for a database that backs up the log several times per day, and one of those backups fails due to an error (see error below) but the subsequent log backups succeed, are those later backups still good, or has the log chain been broken? I am going to arrange to test the backups anyway, but I'd like to know as a matter of background knowledge, and also why or why not the log chain is broken.

    [font="Courier New"]Could not obtain information about Windows NT group/user 'DOMAIN\foo'. [SQLSTATE 42000] (Error 8198)).[/font]

    Thanks in advance for any help! Let me know if you need more information to formulate a response.

    - webrunner

    -------------------
    A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
    Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

  • It shouldn't be broken. If the log backup failed, the log records wouldn't become inactive (because they weren't backed up) and the next log backup should et them (and be twice the size of normal)

    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

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

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