none
The SQL log backup job has detected a discontinuity in the SQL log chain for SQL Server 2014 database database RRS feed

  • Question

  • All,

    Getting the above error backing up SQL..

    "DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for  SQL Server 2014 database database Server\model since the last backup. All incremental backup jobs will fail until an express full backup runs. (ID 30140 Details: Internal error code: 0x80990D11)"

    DPM 2019 RU2

    Cheers,

    LM


    • Edited by Lord Melch Friday, October 2, 2020 9:59 AM
    Friday, October 2, 2020 9:59 AM

Answers

  • Hi,

    The reason incremental backups fail with the Error ID: 30140 - "Discontinuity in log chain" - Is that DPM maintains log chain sequence with every incremental backup.

    This sequence can be broken if user has scheduled native SQL Log backups or has log-shipping enabled (after protection with DPM).

    With these out-of-band log backups the log sequence maintained by DPM is broken and hence the failures seen.

    If you intend to have third-party log backups for databases and also use DPM, you can configure DPM to take only express full backups and no incremental backups (aka log backups).

    The way to do this is to choose the option 'Just before Recovery Point' for incremental backups during Protection group creation/modification.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Lord Melch Friday, October 2, 2020 10:44 AM
    Friday, October 2, 2020 10:22 AM

All replies

  • Hi,

    The reason incremental backups fail with the Error ID: 30140 - "Discontinuity in log chain" - Is that DPM maintains log chain sequence with every incremental backup.

    This sequence can be broken if user has scheduled native SQL Log backups or has log-shipping enabled (after protection with DPM).

    With these out-of-band log backups the log sequence maintained by DPM is broken and hence the failures seen.

    If you intend to have third-party log backups for databases and also use DPM, you can configure DPM to take only express full backups and no incremental backups (aka log backups).

    The way to do this is to choose the option 'Just before Recovery Point' for incremental backups during Protection group creation/modification.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Lord Melch Friday, October 2, 2020 10:44 AM
    Friday, October 2, 2020 10:22 AM
  • Leon,

    Nice one I will give that a go.

    So tick "Just before a recovery point" in the Sync Freq area

    Do I delete ante File Recovery points times in the "Recovery points for files" box and just leave a time in the "Express Full Backup" ?

    Cheers,

    LM


    • Edited by Lord Melch Friday, October 2, 2020 10:52 AM
    Friday, October 2, 2020 10:44 AM